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 Assessment

Gap analysis of an organization's agile methodology implementation

  • Sé el primero en comentar

Agile Methodology Assessment

  1. 1. Agile Methodology: Adoption Assessment Program Management Presentation
  2. 2. | Why are we here today? 1
  3. 3. | 2 Agile Methodology Assessment ▪ Adherence to Scrum methodology ▪ Allocate resources more efficiently ▪ Practice Test Driven Development ▪ Allow QA time to provide better estimates ▪ Automate QA test scripts ▪ Improve team roles and responsibilities ▪ Access to outside team members, e.g., users ▪ Conduct Sprint Retrospectives ▪ Better Acceptance Criteria for User Stories ▪ Backup resources for QA and FE Developer ▪ Establish team norms What we need to improve… ▪ Meet target dates* for product releases ▪ Have tools in place to manage Sprints ▪ Keep track of resource times – time keeping ▪ Established process for release management ▪ No major resource gaps ▪ Conduct feature reviews with product owners ▪ Minimum Dev/QA environmental issues ▪ Makeup of the Sprint team participants What we have done well… Note: * When target date shifts, it is widely communicated to stakeholders so there were no major surprises.
  4. 4. | 3 Agile Methodology Scrum Team Roles Scrum Master Team Members Stake- holders Users Product Owner SCRUM ROLES • Process leader • Scrum Coach • Remove impediments • Facilitate meetings • Develop product increment - Developer - QA - Release Manager • Practice TDD • Review results • Adapt to changes • Provide product guidance and feedback • Attend Sprint Planning meetings • Remove roadblocks • Avoid distractions and disruptions for the team • Provides requirements to Product Owner • Participates in UAT • Signs off on final product increment • Owns product ROI • Prioritize Product Backlog • Ensure team understands product features and requirements - Acceptance Criteria (positive/negative) • Develop user stories/release notes • Provide feedback during review sessions
  5. 5. | 4 Agile Methodology Scrum Team Norms Transparency with Open Communica- tions Criticize the issue not the person Obligation to Dissent Focus only on current Sprint Active Listening Be Respectful Be engaged and focused Seek to understand first No sacred cows Offer solutions along with issues
  6. 6. | UAT A B C D E F G H I User Stories 5 Agile Methodology Scrum Process DAILY SCRUM SPRINT Product Release Sprint Planning Product Backlog Sprint Backlog Sprint Retrospective • Product backlog prioritized by business value • Sprint backlog includes bugs • Team decides what it can commit to deliver • Sprint backlog grooming will further prioritize the order of development/implementation • Scrum Master • Product Owner • Stakeholders • Users • Team Members • 2 to 4 weeks of elapsed time • Iteratively develop/test/re- view/adapt/manage • Level of Effort = Story Points • Velocity = Story Points/Sprint Period • Dynamically adjust workload • Test Driven Development • Weekly Backlog Review • Product increment – delivery of all Product Backlog items during Sprint • Release Notes for clients • Sprint Retrospective - What went well? - What went wrong? - What can we improve? Burndown Chart 1. What have I DONE yesterday? 2. What will I DO today? 3. What are my BLOCKERS?