Concurrency: Past and Present
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Tracking change and innovation in the enterprise software development community
Posted by Stacia Broderick on Jul 13, 2008 06:37 AM
Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)
The End of Middleware: Freedom from IT Stacks as we know it
Six Free Project Management Certification Training Courses
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
The Agile Business Analyst: Skills and Techniques needed for Agile
There is also a very good series on VersionOne's "Agile Chronicles Blog" by Mike Cottmeyer. All the posts in the series are prefixed with "Refactor your PMP". URL of a recent post: http://blog.versionone.net/blog/2008/07/refactor-your-1.html
Maybe it gets better after this. The end point for me was when Stacia fobbed off a question about how scrum deals with thrashing.
Hey, how does waterfall deal with thrashing?
Very good title, but deceiving content. Skip this presentation and go to one of Jeff Sutherland's presentations, such as http://www.infoq.com/presentations/Agile-Management-Google-Jeff-Sutherland
Change control boards! (see Jeff Sutherland's Google presentation which was excellent).
Sorry that the folks posting here have found this presentation to be full of drivel and deceiving. It certainly was not intended to be. I never intentionally "fob off" questions; I care about the perception of the work I do and take these kinds of comments to heart. I will watch this presentation to see where I can improve. If you'd like to email me off line with helpful comments, I am always open to that in the spirit of inspecting and adapting. stacia@agileevolution.com.
Where does your experience about agile come from sina you are so young. if I cannot touch so many projects and how can I prove my agile ability? hi, I like your presentations and your voice
I think, she clarifies what the agile development is. Thank you Stacia
I think the guys criticizing missed the point since the title is clear, it's an Introduction to Agile for Traditional Project Managers. So if you're not a traditional guy and/or you're already acquainted with agile, you might think it's superficial. I think it's good in what it's intended to be, a way to link traditional concepts to agile. Jeff Sutherland's Google presentation is also good and I think both are worth watching.
I had an email exchange with Stephen Cresswell over the weekend who gave me some very helpful feedback on the presentation. I agree that the preamble is a bit long; I promise a better one when I co-present this with Michele Sliger at Agile 08 next month. More importantly, I answered a question and went on a tangent, and it became a bit flubbed. I want to clear the record here so that newbies to agile aren't misguided. I said that "... moving too fast or not fast enough is the ownership of the business or the customer." This is not true. The product owner/customer owns the "What" and the "Why" of the requirements; the speed of delivery is completely up to the team and can be affected by an assortment of constraints and variables. The team and the product owner should work together to find ways to collaborate the best approach under the given circumstances, but at the end of the day, the team should choose a pace that is sustainable, iteration after iteration - a pace that results in high quality software increments. I hope this clarifies and dissuades any potential confusion. That's the thing about videos: they're permanent. :) And to ma mz: I'm not as young as you think I look.
I'll vouch for the age-defying effects of Agile!
There's something to be said for an approach that reduces stress and increases the pleasure of a job well done :-)
deb
(age: 96)
Brian Goetz discusses the difficulties of creating multithreaded programs correctly, incorrect synchronization, race conditions, deadlock, STM, concurrency, alternatives to threads, Erlang, Scala.
Often the hardest part of changing technologies is language syntax differences. This new article provides Java developers with a transition guide to Actionscript which forms the foundation of Flex.
Neal Ford talks about having multiple languages running on one of the two major platforms: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
David Anderson talks about the history of Agile, the current status of it and his vision for the future. The role of Agile consists in finding ways to implement its principles.
Nick Sieger talks about the future of JRuby, Java Integration, and his work on JEE deployment tools for Ruby on Rails like Warbler.
Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
11 comments
Reply