Simple Model for Agile Development
Agile is not a process but a mindset. Agile is a better way to write software and build systems focused on customer satisfaction. With leadership buy-in and proper implementation, an agile mindset will deliver quality quickly and at a reduced cost. When your team, project, or program agrees to do agile development, you are agreeing to the statements in the Agile Manifesto.
The Agile Manifesto reads:
We are uncovering better ways of developing software by doing it and helping others do it; through this work, we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Many software development teams find themselves wanting to or directed to making the transition to agile but are not sure how to get started. The purpose of this paper is to generalize and simplify the roles, responsibilities, meetings,and iteration cycles so that an agile team can easily begin to implement their own agile process that works for their team, clients, customers, and users.
Scrum, XP (Extreme Programming), FDD (Feature Driven Development), AUP (Agile Unified Development), and
Please log in or sign up below to read the rest of the article.