Agile software projects deliver business value by embracing change. Whatever business gains, this puts extra responsibility on project management. How to control resources in forever evolving conditions? How to ensure clarity and precision of cost calculations? On the other hand, every stakeholder wants to know whether the project will be on time/within budget. Uncertainty about using Agile is still strong since Scrum methodology doesn’t provide guidelines on cost and schedule control.
Have you found yourself at the crossroads? Tearing between Agile and Waterfall? Caught off-balance by the recent stats showing Agile software projects to be over three times as popular as Waterfall? They also have over three times as many successful outcomes. Does that mean that Waterfall has outstayed its welcome? Our take: that depends. Every particular situation calls for a specific solution. It’s best to take a balanced approach and consider what really matters.
At last the requirements are gathered, the project is sized and everyone’s restless to get the ball rolling. Now even one optimistic glance at the long list of user stories makes you certain they’re impossible to accomplish within the given time frame. So our next stop is prioritization of the Product Backlog.