Beyond Traditional "Waterfall" Model:
Traditional development with single-function groups, delayed or weak feedback loops, front-loaded predictive planning, and a sequential flow from analysis to test is not very successful in today’s volatile world. This approach delays feedback, learning, and potential return on investment due to an absence of real working software until late in the game, causing a lack of transparency, lack of ability to improve, reduction in flexibility, and an increase in business and technical risks.Waterfall (or) Traditional Model Flow:
An alternative – cross-functional teams with iterative development – has also existed for decades, but
was not as widely used as the traditional model.
Scrum packages proven product-development concepts in a simple framework, including: real teams, cross-functional teams, self-managing teams, short iterative full-cycle feedback loops, and lowering the cost of change. These concepts increase agility and feedback, enable earlier ROI, and reduce risk.
0 comments:
Post a Comment