Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Agile methodology

125 visualizaciones

Publicado el

In traditionally planned projects – we typically try and understand all of the requirements up front in order to estimate cost and schedule. We then aggressively managed changes to requirements so we could deliver on our cost and schedule estimates.

For agile we assume date is fixed and cost is also fixed (can only add so many developers to a project without slowing everything down) and we focus on delivering the most valuable requirements or Features.
We don’t plan for too much at a time. We don’t want to plan too far ahead because it is wasted effort if we don’t actually do the work on those features. We want to add more detail, incrementally as we get closer to execution.

Publicado en: Empresariales
  • Inicia sesión para ver los comentarios

  • Sé el primero en recomendar esto

Agile methodology

  1. 1. Agile world - Product vision to continuous delivery planning (Scrum framework) Author :- Sumit Sinha – Senior Business Consultant CSM (Certified Scrum Master®) https://ie.linkedin.com/in/sumit-sinha-csm®-epgbm-iim-calcutta-78aaa519
  2. 2. Waterfall vs. Agile Source: Jim Highsmith Work to maximize the value delivered in the shortest timeframe possible Waterfall – Requirements are more Fixed – Resources and Time are more Variable Agile – Resource and Time are more Fixed – Features are more Variable
  3. 3. Product Vision Product Roadmap High Level Release Plan Sprint Plan Agile Approach to Planning… Agile Takes an Iterative Approach to Planning  Strategic turns Tactical  Vision to execution  Time period shortens  Years to days Daily Plan  We plan as much as we have visibility into  We plan continuously throughout the release
  4. 4. Backlog to Delivery…. Functionality of Agile, Scrum
  5. 5. Scrum Framework – Roles, Ceremonies & Artifacts Scrum Framework •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Ceremonies •Product backlog •Sprint backlog •Burndown charts Artifacts
  6. 6. Sprint backlog… Do’s…..  Involve every team member in the process  Discuss how every item should be implemented.  Have a definition of done  Identify all kinds of tasks.  Review the sprint commitment.  Evolve the Sprint Backlog during the sprint. Don’t  Don't estimate tasks at all.  Don't assign tasks up front.  Don't use too much time. The sprint backlog is a simple list of the tasks that must executed by the team in order to deliver an increment of functional software at the end of that sprint. Sprint backlog creation happens in the second part of the sprint planning meeting with the participation of every team member.
  7. 7. “Definition of Done” represent by V - Model
  8. 8. Next Steps Building a Definition of Done
  9. 9. Backlog - Work Flow

×