BSA 375 Week 3 DQ 2 - test results Risks are reduced in...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Scrum methodology for software applications is built on the basis of agile development philosophy, which  promotes the use of coding and management procedures that are both flexible and lightweight. Instead of  making project specifications rigid up-front, scope is given to redefine and shape them based on inputs  taken from stakeholders, including customers as the process goes through the later stages. Flexibility  comes through the scope given to developers to have daily meetings, adjust their activities, and redirect  their project by collaborating with stakeholders. In terms of traditional methods, project specifications in  agile development are not set in stone at the beginning but are modified incrementally based on software 
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: test results. Risks are reduced in agile development because change management is done throughout the process in response to the associated business markets and environments. Feedback from stakeholders, including customers is taken throughout, to make changes to design, timelines, and budgets. Teams in agile development are allowed to self organize, and are 5-9 people in size when compared to traditional methods, where teams could be large and have little awareness of the overall project objectives. Communication is the lifeblood of agile development as it allows developers to make adjustments to their activities based on aspects that other team members are working on....
View Full Document

This note was uploaded on 11/21/2011 for the course BSA/375 BRBSIT911 taught by Professor Shawnpullum during the Spring '10 term at University of Phoenix.

Ask a homework question - tutors are online