why_should_we_consider_moving_to_agile
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
why_should_we_consider_moving_to_agile [2016/02/10 13:30] – created hpsamios | why_should_we_consider_moving_to_agile [2020/06/04 11:35] (current) – Removed LINKBACK hans | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Why Should We Consider Moving to Agile? ====== | ====== Why Should We Consider Moving to Agile? ====== | ||
- | For organizations that are not happy with the delivery of their software | + | For organizations that are not happy with the delivery of their software projects, Scrum / Agile is an approach |
An Agile / Scrum approach achieves this by: | An Agile / Scrum approach achieves this by: | ||
- | * Ordering the delivery of functionality based on the "most important value first" principle. | + | * Ordering the delivery of functionality based on the "most important value first" principle, prioritizing our demand based on sound economic principles. |
+ | * Organizing our system of delivery around the " | ||
+ | * Delivering value in short iterations (also called sprints - 1-4 week time-boxes) to a known quality standard so the decision to release can be made at any time (usually when it is determined that sufficient functionality is provided). In other words, " | ||
* Delivering value piece by piece so that customers can provide feedback as the work is completed. | * Delivering value piece by piece so that customers can provide feedback as the work is completed. | ||
- | * Ensuring there is transparency of progress and constant communication between the people who need something and the people that can provide it. | + | * Ensuring there is transparency of progress and constant communication |
- | * Ensuring that we build plans based on the real capacity of the organization to deliver | + | * Ensuring that we build plans based on the real capacity of the organization to deliver. |
+ | Unlike the traditional development approach, which assumes that you plan a software project upfront and in detail, Agile / Scrum approaches understand that the real world of software is a place where: | ||
+ | |||
+ | * The customer does not (and cannot specify) exactly what he / she wants, but rather will be able to provide solid feedback when they see a running system. | ||
+ | * Our teams have potentially lots of ways to build a capability but it is when they start working on the capability, with the whole team (development, | ||
+ | * That change will happen and, more importantly, | ||
+ | |||
+ | |||
+ | {{tag> | ||
- | {{tag> |
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/why_should_we_consider_moving_to_agile.1455139804.txt.gz · Last modified: 2020/06/02 14:28 (external edit)