Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • do_we_need_points_to_generate_a_release_burn-up_chart
why_should_we_consider_moving_to_agile

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
why_should_we_consider_moving_to_agile [2016/02/10 13:47] – [Why Should We Consider Moving to Agile?] hpsamioswhy_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 development projects, Scrum / Agile is an approach made up of values, principles and specific practices that can help you deal with the constant need to change direction while still maintaining control, to dramatically decrease your time-to-market, to reduce the risk of working with complex projects, to improve the quality of delivery so your customers see fewer defects, while also increasing the engagement and morale of your people.+For organizations that are not happy with the delivery of their software projects, Scrum / Agile is an approach made up of values, principles and specific practices that can help you deal with the constant need to change direction while still maintaining control, to dramatically decrease your time-to-market, to reduce the risk of working with complex projects, to improve the quality of delivery so your customers see fewer defects, while also increasing the engagement and morale of your people.
  
 An Agile / Scrum approach achieves this by: An Agile / Scrum approach achieves this by:
Line 7: Line 7:
   * Ordering the delivery of functionality based on the "most important value first" principle,  prioritizing our demand based on sound economic principles.   * 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 "delivery of value to the customer."   * Organizing our system of delivery around the "delivery of value to the customer."
-  * 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 it is determined that sufficient functionality is provided). In other words "deliver on a cadence, release on demand".+  * 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, "deliver on a cadence, release on demand".
   * 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 / collaboration especially between the people who need something and the people that can provide it but throughout the whole delivery system.   * Ensuring there is transparency of progress and constant communication / collaboration especially between the people who need something and the people that can provide it but throughout the whole delivery system.
Line 14: Line 14:
 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: 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 system that is running in front of them. +  * 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, QA, documentation, BA, etc), that they will really understand how to solve the problem and deliver the value.+  * 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, QA, documentation, BA, etc.), that they will really understand how to solve the problem and deliver the value.
   * That change will happen and, more importantly,  that change is a good thing as it means we have learned something about the requirements or the approach we are taking, and we should leverage that knowledge. This means Agile / Scrum approaches work to make the cost of change low.    * That change will happen and, more importantly,  that change is a good thing as it means we have learned something about the requirements or the approach we are taking, and we should leverage that knowledge. This means Agile / Scrum approaches work to make the cost of change low. 
  
  
-{{tag>Consultant Tools CultureChange Organization ElevatorPitch Why FAQ}}+{{tag>Consultant Tools CultureChange Organization ElevatorPitch Why FAQ PresentationIdea}} 
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/why_should_we_consider_moving_to_agile.1455140874.txt.gz · Last modified: 2020/06/02 14:32 (external edit)