1_Agile and Scrum Framework_2024.pptx

1 Agile and Scrum Training Confidential  2 Agenda 1 Agile and Scrum 2 Requirements in Scrum 3 Planning in Scrum  3 Goals Novice Intermed...

1 Agile and Scrum Training Confidential  2 Agenda 1 Agile and Scrum 2 Requirements in Scrum 3 Planning in Scrum  3 Goals Novice Intermediate Experts get the get the whole know more about knowledge of picture “aerobatic flying”, Scrum hints and tricks you may never heard about  4 So, What is Scrum? Confidential  5 Scrum is an Agile process that allows us to focus on delivering the highest business value in the shortest time.  6 It allows us to rapidly and repeatedly inspect actual working software (every one week to one month).  7 Process Organization The business sets the Every one week to a month priorities. Teams self- anyone can see real working organize to determine the software and decide to best way to deliver the release it as is or continue to highest priority features. enhance it.  8 Brief History Confidential  9 Individual Approach Confidential  10 Sequential Process Requirements Design Implementatio n Verification Maintenance  11 Why did sequential approach work THEN? Less frequent market changes Repeatable approach Fixed price/budgeting Confidential  12 Why doesn’t sequential approach work NOW? The cost of change is high Product fails expectations Time-to-market is long Product can become obsolete Confidential  13 Iterative Process Iterative Deployment Business value is delivered incrementally in time-boxed cross-discipline iterations. Business Modeling Requirements Analysis and Design Implementation Test Deployment Tim e  14 Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others to 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 tothere That is, while change overinfollowing is value the itemsaon plan the right, we value the items on the left more.  15 Individual Approach Confidential  16 Working Software Confidential  17 Customer Collaborati Confidential on  18 Responding to Changes Confidential  20 Agile: Practices DSDM FDD Lean Crystal Kanban XP Scrum  23 Traditional Project Hey, stop Requirements deploying! Design What? Can’t hear you. Code Test Deploy 6 months  23 Agile Scrum Sprints (Iterations) Requirements Requirements Requirements Design Code Design Code Design Code Test Deploy Test Deploy Test Deploy 2 weeks 2 weeks 2 weeks  23 Sprints Scrum development makes progress in a series of iterations (called “sprints”). Constant duration, 1–4 weeks. Product is designed, coded, tested and documented during the sprint. No changes during sprint!  23 Waterfal l Scrum is Not a Mini- Scrum Waterfall Confidential  23 Scrum Framework Roles Meetings Artifacts Sprint Planning Sprint Review Product, release Product Owner Sprint and sprint Team Retrospective backlogs Scrum Master Daily Standup Burndown charts Backlog Scrum Board Grooming  25 Scrum Roles Confidential  21 Product Owner Accepts or Responsible for rejects work the profitability results. of the product. Has the vision Defines the of the product. features of the product. Decides on Prioritizes release date and features according content. to market value.  21 The Team Cross-functional Ideally, no titles self-organizing but rarely a group of 5-9 possibility. people. Attempts to build Membership a “potentially should change shippable increment” each only between Sprint. sprints. Members should be full-time (may be exceptions, e.g., DBA)  22 The Scrum Master Responsible for Enables close enacting Scrum cooperation values and across all roles practices. and functions. Not manager, but shields the Removes team from impediments. external Ensure that the interferences. team is fully functional and productive.  23 Scrum Artifacts Product Sprint Backlog Increment Backlog  24 Product Backlog Product Backlog Item High-priority Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Low-priority  25 Release Backlog Product Backlog Item Product Backlog Item Product Backlog Item Release Backlog Product Backlog Item Product Backlog Item Release #1 Product Backlog Item Release #2 Product Backlog Item  26 Scrum Task Board In To Do Done Progress Product Backlog Item Product Backlog Item Product Backlog Item  27 Burndown Chart Estimated Hours, Total Days in current Sprint  34 Scrum Meetings Confidential  29 Sprint Meetings Sprint Planning Daily Scrum Backlog Grooming Sprint Review Sprint Retrospective  30 Sprint Meetings  31 Sprint Planning Product Product Backlog Item Product Backlog Item Sprint Product Backlog Item Backlog Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item  32 Sprint Planning Sprint Technical Backlog Product Backlog Item Tasks Estimated Product Backlog Item time: Product Backlog Item 2 weeks total Are we able to do this? Yes! We commit to do this.  33 Daily Standup I have some problems with my Okay, I’ll think what task… can be done about that problem. Here is what I did yesterday… I will work today on that task…  34 Backlog Grooming Product Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item  35 Sprint Review Product Backlog Item Product Backlog Item Product Backlog Item Product Backlog Item Backlog Item (Not Done) Backlog Item (Not Done)  36 Sprint Retrospective What did we learn? What can we do better? Action Items: 1. … 2. … 3. … 4. …  38 Helicopter View from Scrum  39 Exercise: Build Your Scrum Form the teams. Use sheet of paper, scissors, scotch tape, and handouts to recreate Scrum workflow. Share the work with others after 45 minutes.  40 New Challenges With Scrum Learning new Learning to think Learning how to Unlearn things. technical skills. and work as a create working team. software within short time boxes.  41 Why Do Teams Love Scrum? Not completing the tasks from Ownership and manager, but autonomy. understanding the team’s goals. Higher visibility and fast Fun factor☺ feedback. Collaboration and mutual aid.  42 Scrum Is About Changing Minds Great products Provide just come from enough great teams. documentation to produce great work. Involve end-users, Existing in a decision-makers, and mindset that is stakeholders throughout always ready for entire process. change.  43 Improved Stakeholder Satisfaction Development team aligned to business goals. Easy to manage changing Risks are requirements. continuously reduced. Improved project visibility. Higher quality.  44 Why Does Business Buy Scrum? We can easily adapt at any Our needs changed moment and show you the interim results. You can touch working software at I’m not sure you can any stage we are budding what we build what I need need. We can give you the time range I can’t see the when it is finished. We use timeframes and continuous planning with focus on milestones working software. We use proven technical I’m afraid it is too practices and buggy and poorly continuously improving maintainable our approaches.