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?
Case Study: IBM's Agile Transformation
Agility at scale, become as agile as you can be
Maximize your business-responsiveness with Mingle. Provide your global development team a shared space that adapts to the way they work.
...and somewhat cultish.
Why said like that?
Our team management is changing to Agile, is there no difference with waterfall??
Why said like that?
Our team management is changing to Agile, is there no difference with waterfall??
There is a difference. But, many organizations use Agile in waterfall way. The sad part is they don't know about it.
Can this link be fixed?
Overall, the first half of the presentation is a must-hear for anybody who is wondering why they should care about Agile/Lean.
Scott presents very interesting results of a Dr Dobbs 2008 survey:
THANKS!
PS: I completely missed the point with Modeling and TDD. Can anybody shed some light on this?
Having a look to the "Agile Project Success Rates %" slide there are 539 agile projects, which combined with the previous ones gave me a maximum of 125 companies (not hundreds by the way). I might miscalculated it, but if I am true, do you know any other report based on a higher number of surveys, please?
Cheers!
This recent news item points you to a recent, larger survey by VersionOne software. Their sample did include companies NOT using their software.
Sorry, not sure which link you mean. Please email me the url at deborah@infoq.com and I'll get it out there. Thanks!
I think Scott tried to relate or compare the concepts of Design using UML / Modeling techniques vs the generation of the Design by using Test Driven Development and Refactoring.
The basic idea in this sense is that before agile practices, the design was made by taking the requirements as input, applied some techniques and generate the design (and architecture) using models/diagrams as the main output artifact.
While if you use TDD, it comes that the design emerges as consequence of the continuous application and evolution of doing Unit Testing and Refactoring to the code you write.
Thank you Carlos. What is Scott's point regarding these practices in real life? Why oppose both techniques?
Specifying tests should not prevent people from creating some models? I agree that tests are more important than models, but models are still very often required as an aid to development, team members coordination and maintenance...
I guess I will have to listen to that part again... :-)
Olivier,
I believe the point Scott was making is that since the majority of professing agilists don't do TDD then TDD is not a good practice and the converse is true for modeling.
The person in audience questioned the validity of the survey because the majority of respondents do detailed documentation. In my opinion, that is a good question and Scott didn't answer it to my satisfaction.
Maybe Scott's point is that the agile practices that are not adopted by the masses should be cut?
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