One of the biggest differences in software development between a phased waterfall approach and Agile Scrum is the fundamental assumptions about the backlog. Regardless of the methodology, all projects have a list of features, bugs and technical issues that require work. It is the backlog. Executing on this list of items is the work at hand. It is the project. We know that the total analysis effort with waterfall is spent up front by reviewing requirements and supporting artifacts supplied by the stakeholders and other SMEs. The backlog requirements are consumed in total up front with the assumption that the features contained in the backlog are sufficient to guide us to project completion with a state of delighted users.
I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
This article is related to
agile,waterfall,backlog,agile benefits,agile aproach,agile concepts
agile,waterfall,backlog,agile benefits,agile aproach,agile concepts
No comments:
Post a Comment