Applying Agile Methodology Harmeet Sudan PMP Waterfall vs

Applying Agile Methodology - Harmeet Sudan, PMP

Waterfall vs. Agile The Waterfall approach to product development may conflict with the goals of maximum speed and flexibility. Instead a holistic or “rugby” approach – where a team tries to go the distance as a unit, passing the ball back and forth – may better serve today’s competitive requirements.

The Agile Manifest – a Statement of Values Individuals and interactions over Process and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan

Sequential vs. overlapping development Requirements Design Code Test Rather than doing all of one thing at a time. . . Scrum teams do a little of everything all the time

Scrum in 100 words � Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. � It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). � The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. � Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

Characteristics of Scrum � Self-organizing teams � Product progresses in a series of month-long “sprints” � Requirements are captured as items in a list of “product backlog” � No specific engineering practices prescribed � Uses generative rules to create an agile environment for delivering projects � One of the “agile processes”

Scrum 24 hours Sprint 2 -4 weeks Sprint goal Return Cancel Return Gift Coupons wrap Gift Cancel wrap Product backlog Sprint backlog Coupons Potentially shippable product increment

Putting it All together

The Planning Onion Strategy Portfolio Product Release Iteration Daily � � Agile teams plan on the innermost three levels. Others (on the team in the company) plan on the outer three levels.

An Agile Approach to Planning Release Conditions of Satisfaction (scope, schedule, resources) Feedback Release planning Iteration Feedback Conditions of Satisfaction (scope) Iteration planning Developme nt Product increment

Relating the Different Planning Levels Iteration 2 Iteration 1 Product Backlog As a frequent flyer, I want to… 3 As a frequent flyer, I want to… 5 As a frequent flyer, I want to… 2 Iteration Backlog Code the UI 8 Write test fixture 6 Code Middle tier 12 Write tests 5 Automate Tests 4 “Yesterday I started on the UI; I should finish before the end of today. ”

Sprints � Scrum projects make progress in a series of “sprints” ◦ Analogous to Extreme Programming iterations � Typical duration is 2 -4 weeks or a calendar month at most � A constant duration leads to a better rhythm � Product is designed, coded, and tested during the sprint

No Changes During a Sprint C h a n g e • Plan sprint durations around how long you can commit to keeping change out of the sprint

Scrum framework Roles • Product owner • Scrum. Master • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts

Scrum framework Roles • Product owner • Scrum. Master • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts

Scrum Roles Role Description Product Owner §Define the features of the product §Decide on release date and content §Be responsible for the profitability of the product (ROI) §Prioritize features according to market value §Adjust features and priority every iteration, as needed §Accept or reject work results Scrum. Master §Represents management to the project §Responsible for enacting Scrum values and practices §Removes impediments §Ensure that the team is fully functional and productive §Enable close cooperation across all roles and functions §Shield the team from external interferences Team §Typically 5 -9 people §Cross-functional: §Programmers, testers, user experience designers, etc. §Members should be full-time §May be exceptions (e. g. , database administrator §Teams are self-organizing §Ideally, no titles but rarely a possibility §Membership should change only between sprints

Scrum framework Roles • Product owner • Scrum. Master • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts

Sprint Planning � Team selects items from the product backlog they can commit to completing � Sprint backlog is created ◦ Tasks are identified and each is estimated (1 -16 hours) ◦ Collaboratively, not done alone by the Scrum. Master � High-level design is considered As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)

The Daily Scrum � Parameters ◦ Daily ◦ 15 -minutes ◦ Stand-up � Not for problem solving ◦ Whole world is invited ◦ Only team members, Scrum. Master, product owner, can talk � Helps avoid other unnecessary meetings

Everyone Has Three Questions What did you do yesterday? What will you do today? Is anything in your way? � These 1 2 3 are not status updates for the Scrum. Master ◦ These are commitments in front of peers

The Sprint Review � Team presents what it accomplished during the sprint � Typically takes the form of a demo of new features or underlying architecture � Informal ◦ 2 -hour prep time rule ◦ No slides � Whole team participates � Invite the world

Sprint retrospective � Periodically take a look at what is and is not working � Typically 15 -30 minutes � Done after every sprint � Whole team participates ◦ ◦ Scrum. Master Product owner Team Possibly customers and others

Start / Stop / Continue • Whole team gathers and discusses what they’d like to: Start doing Stop doing This is just one of many ways to do a sprint retrospective. Continue doing

Scrum framework Roles • Product owner • Scrum. Master • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts

Product backlog • The requirements • A list of all desired work on the project • Ideally expressed such that each item has value to the users or customers of the product This is the product backlog • Prioritized by the product owner • Reprioritized at the start of each sprint

A Sample Product Backlog item Estimate Allow a guest to make a reservation 3 As a guest, I want to cancel a reservation. 5 As a guest, I want to change the dates of a reservation. 3 As a hotel employee, I can run Rev. PAR reports (revenue-per-available-room) 8 Improve exception handling . . . 8 30 50

The sprint goal • A short statement of what the work will be focused on during the sprint Life Sciences Database Application Support features necessary for population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real-time, streaming data.

Managing the Sprint Backlog � Individuals sign up for work of their own choosing ◦ Work is never assigned � Estimated work remaining is updated daily � Any team member can add, delete or change the sprint backlog � Work for the sprint emerges � If work is unclear, define a sprint backlog item with a larger amount of time and break it down later � Update work remaining as more becomes known

A sprint backlog Tasks Mon Tues Wed 8 4 8 Code the middle tier 16 12 10 4 Test the middle tier 8 16 16 11 8 8 8 4 Code the user interface Write online help 12 Write the foo class 8 Add error logging Thur Fri

Hours A sprint burndown chart

Tasks Mon Tues Wed Thur 8 16 8 12 Code the user interface Code the middle tier Test the middle tier Write online help 4 12 16 8 10 16 7 11 50 Hours 40 30 20 10 0 Mon Tue Wed Thu Fri 8

Scalability � Typical individual team is 7 ± 2 people � Factors in scaling ◦ Scalability comes from teams of teams ◦ ◦ Type of application Team size Team dispersion Project duration � Scrum has been used on multiple 500+ person projects

Scaling through the Scrum of scrums

Scrum of scrums

Recap

Product Owner explains the Scope

Team estimates the complexity and task details

Sprint Review

Sprint Demo

Daily Scrum

Daily Scrum – Contd…

Product Backlog

Sprint Backlog

Typical Scrum Board

Typical Scrum Board – Contd…

Agile Tool Demo

Enterprise Product Tour Video – Version. One � https: //vtv. v 1 host. com/11/? edition=enterprise&r elease=11. 3&page=Main. Menu. My. Home

Next Steps

Presentations and Discussion � � Effective User Stories for Agile Requirements Estimation Techniques Agile for Testing Agile for Program Management Office

Appendix

Sources � www. mountaingoatsoftware. com/scrum � www. agilemanifest. com � “The New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

Product Backlog Template Functio nal/No n. Release Sprint Req Functio Feature No No No nal Name User Business Value Estimation Error Description Priority (BV) ate Risk Severity Total Points 0 0 Origin Creation ator Date Created Closed By Status Date

Sprint Plan Template Sprint Planning from 5 -Oct-2009 to 30 -Oct-2009 Sl. No Phase Name Task Description Assig ned Effo PSD PED To rts Status WEBSITE REDESIGN - DESKTOP VERSION - POST DEPLOYMENT TASKS Week 1 Onsite Team Offshore Team T 1 T 1 T 2 T 3 T 4 T 5 T 6 T 7 T 8 T 9 T 10 T 11 T 12 3 4 T 15 T 16 T 17 T 18 T 19 T 20 T 21 T 22 T 23 Total Efforts 1 0 8 24 0 0 39. 5 0 0 8 0 0 0 17 35 1 Design SEO 22 -Oct-09 26 -Oct-09 ALL 20 Closed 2 Design Progress bar, Button and Form design for User registration 22 -Oct-09 26 -Oct-09 ALL 20 Closed 3 Roll Out Virginia and Tenesse zips not launching those site 5 -Oct-09 6 -Oct-09 ALL 24 Closed 4 4 Roll Out Change Label Coler from Red to Blue 5 -Oct-09 7 -Oct-09 ALL 3 Closed 1 5 Roll Out Shows Incorrect in Safari on Mac 5 -Oct-09 7 -Oct-09 ALL 5 In Progress 4 6 Roll Out Sometimes get error on page warning when going back 5 -Oct-09 7 -Oct-09 ALL 32 Closed 12 2 7 Roll Out Copyright should be Changed to Copyright(mark) 2009 Alfa Mutual Insurance Company 5 -Oct-09 7 -Oct-09 ALL 16 Closed 2. 5 4 8 Roll Out Requirement missed as part of project execution 5 -Oct-09 21 -Oct-09 ALL 80 Closed 1 9 Roll Out Need to be able to press enter instead of clicking execute button 5 -Oct-09 7 -Oct-09 ALL 5 Closed 3 1 6 10 Roll Out FAQ, if you click on multiple FAQ's - Error on Page 5 -Oct-09 7 -Oct-09 ALL 32 Closed 3 11 Roll Out Tracking Script is Commented Out 5 -Oct-09 6 -Oct-09 ALL 20 Closed 3 4 12 Roll Out Billmatrix page is centered in IE 7 but is left aligned in other browsers 5 -Oct-09 8 -Oct-09 ALL 30 In Progress 4 13 Roll Out The mouse pointer no longer changes when you mouse over the action button 12 -Oct-09 13 -Oct-09 ALL 6 In Progress 14 Roll Out All banners have to load before site starts 5 -Oct-09 14 -Oct-09 ALL 64 Closed 15 Roll Out If you select as state then do agent locator and come back text is gone? 5 -Oct-09 14 -Oct-09 ALL 40 Closed 16 Roll Out All tickers have to load before site starts 5 -Oct-09 14 -Oct-09 ALL 64 Closed 17 Roll Out Application urls and emails need to be looked UP From Table by Environment, Not Hard Coded. For example customer stories email 5 -Oct-09 14 -Oct-09 ALL 64 In Progress 1 18 Roll Out These are high maintenance, need to pull from common file 5 -Oct-09 28 -Oct-09 ALL 80 In Progress 1 15 -Oct-09 28 -Oct-09 ALL 60 Closed 5 -Oct-09 30 -Oct-09 ALL 100 In Progress "FARMS" to be re-located from under Home to Top of the menu list. Should reflect in all pages which has left handside navigation menu. "Auto, Home, Life, Farm" to be the order. 0 0 0 0 24 0 0 5 2 6 4 1 6 3 "Farm" to be renamed as "Farms" - Will confirm this 19 Roll Out 20 Roll Out Review efforts on Roll Out tasks WEBSITE REDESIGN - MOBILE SITE 21 Design 22 Construction Total Efforts Creation of i. Phone New Application design 1 0 28 -Oct-09 29 -Oct-09 ALL 20 Closed 7 -Oct-09 16 -Oct-09 ALL 20 Closed 0 8 24 8 0 0 0 8 4 0 0 0 45 0 i. Phone to Non-i. Phone HTML Migration for New design 10 24