10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Five Key Practices to Agile ALM
Transforming Software Delivery: An IBM Rational Case Study
18 agile and lean practices for effective software development governance
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
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: blog.versionone.net/blog/2008/07/refactor-your-...
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 www.infoq.com/presentations/Agile-Management-Go...
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)
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
11 comments
Watch Thread Reply