Agile Perfomance Metrics
More Productive
Faster Time To Market
Less Defects
Agile Performance Metrics
The QSM Associates in their "Agile Impact Report, Proven Performance Metrics from the Agile Enterprise" have assessed the performance of Agile development projects against a database of 8,000+ primarily traditional development project in three key areas: productivity, time-to-market and quality.
The results were that teams using Agile were 50% faster to market, 25% more productive, with one quarter the number of defects.
Is it true? And if it is, why?
Why is Agile Time to Market (TTM) Delivery 50% Faster?
According to our enterprise release schedule, we are supposed to deliver major release every nine months. However very frequently not everything is going according to our release plan. Last time, our major release was delayed more than ten months, and release date had been moved five times. Our shareholders and our customers were frustrated by our inability to deliver on schedule.
Why are Agile Teams 25% More Productive?
What if you could provide such environment that your software development team is 10-20% more productive?
The potential benefits could be enormous, from saving achieved on labour cost, to faster time to market.
But what if you could boost productivity 25% or more!?
Yes, you can!
The Quest For Exceptional Software Quality
Rolex, the fine piece of Swiss jewelry. The first wristwatch awarded the class “A” precision certificate. It has been passed from generation to generation, and is still ticking today with precision to 1 sec!
Yes, it takes years to build the renowned brand name, that everyone associates with the innovative products with exceptional quality.
Needless to say that those products fulfill their intended functionality and are free of defects.
The name implicitly says it all. The Rolex wristwatch is synonymous for precision and quality.
Agile Transformation
High Productivity and Exceptional Quality are Just Half the Story
Written by Ned Kremic
Many organizations are embracing the agile process framework, looking for the “magic formula” for higher productivity and an exceptional quality.
The delivery teams control both productivity and the quality. Short iterative and incremental deliveries guarantee the higher productivity, and by integrating the quality into the development process, those teams have historically achieved much better, if not the outstanding quality.
Agile Requirements
Horizontal and Vertical User Stories - Slicing the Cake
Written by Ned Kremic
User stories are an agile approach to requirements.
User story is description of functionality as seen from user perspective of the system (“I want to withdraw $100 from my checking account”), not from perspective of a developer of the system (“the system shall tokenize the bank card number...”). Which is exactly what its name implies “the user story” not just “the story”!
The primary purpose of the user story is to let the user express in clear, unambiguous, non-technical language what she really wants, so that all stakeholders involved in a story implementation could understand it.
Agile Quality
The Quest For Exceptional Software Quality
Written by Ned Kremic
"or how to achieve the outstanding software quality"
What is quality?
Probably the last thing that will come to your mind would be the actual definition of quality.
Most likely you will think about synonyms of quality: Lexus, Swiss Watch, iPod/iPhone/iPad (Apple products) or something similar?
Agile Planning
Agile Estimation
Written by Ned Kremic
Estimation is an essential part of any project management activity.
Agile is no different, we have to estimate for scoping, scheduling and budgeting.
However the planning and estimation between traditional waterfall process based on PMI PMBOK and Agile approach are quite different.
Why?
