Adaptive Development Methodology
Download as PPT, PDF11 likes10,656 views
The document provides an overview of the Adaptive Development Methodology (ADM), which is a modified Scrum/XP approach used specifically for product development at Salesforce. It describes key aspects of ADM including principles like iterative development, transparency, and eliminating waste. It also outlines roles, ceremonies, and artifacts of the Scrum framework that ADM is based on such as sprints, daily stand-ups, product backlogs, and sprint planning.
Adaptive Development Methodology
- 2. Overview Outline History ADM Overview ADM Principles & Mechanics
- 3. The Backstory Fast Innovative Successful Growing
- 4. 7 years later… 35,000+ customers 900,000+ subscribers 100+ Million transactions per day 200+ in Technology!
- 5. But…uh oh…
- 7. … to get things done…
- 8. … so what’s the deal? Waterfall process Un-predictable Delayed releases Velocity slowdown No visibility Late feedback Technical Debt Death march Loss of cred Over budget Scope creep
- 9. … so what’s the deal? Waterfall process Team frustration
- 10. … so what’s the deal? Waterfall process Team frustration
- 11. Not good…
- 12. We can do better…
- 13. ADM Elegant… … and a little messy
- 14. Overview Outline History ADM Overview ADM Principles & Mechanics
- 15. Core Values KISS Listen to your customers Iterate
- 16. What is ADM? ADM is a modified Scrum/XP style of product development that is specific to Salesforce. It employs Scrum project management framework and adopts certain XP practices.
- 17. What is ADM? Re-factoring Self-organizing Predictable releases Transparent Ftest - Selenium Continuous integration Debt free Just-in-time Iterative Always Potentially Releasable Time-boxed User stories Agile Lean Early feedback Code Reviews Collective Code Ownership Self-correcting
- 18. What is Scrum? An agile project management framework for developing software Simple Prioritized work Time-boxed, 30-day sprints
- 19. Self-organized, empowered teams Daily, verbal communication Potentially “production quality” every 30 days What is Scrum?
- 20. Eliminates waste Increases throughput Provides transparency What is Scrum?
- 21. Overview Outline History ADM Overview ADM Principles & Mechanics
- 22. Scrum Lifecycle Daily Scrum Meeting Sprint Review: Demo Potentially Releasable New Functionality Product Backlog Sprint Backlog Retrospective 24 Hours 2 - 4 Weeks
- 23. The Scrum Team QE Engineer Developer Developer QE Engineer Developer Tech Writer UE Designer Product Owner
- 24. Roles: Product Owner Single throat to choke Fully accountable for the success or failure of the scrum team
- 25. Roles: Product Owner Owns and prioritizes Product Backlog Leverages team to break down Product Backlog Creates Release Backlog by targeting priority Product Backlog Directly drives development Fully engaged
- 26. Roles: ScrumMaster Ensures Scrum Team lives by the principles and practices of Scrum Removes obstacles Coach
- 27. Roles: ScrumMaster Protects team from external influences Improves productivity of team so each user story is potentially releasable Keeps progress information up-to-date and visible to all Facilitates Daily Meetings
- 28. Roles: Scrum Team Cross-functional team Has tasks on the Sprint Backlog Self organizing, Self correcting. Teams decide best way to deliver Makes their own commitment with the resources available, decides how best to distribute tasks to team members Members are dedicated resources (as much as possible) Optimally 6-10 people
- 29. Product Backlog Key to success of Scrum Master list of functional and non-functional items desired in the product (features, bugs, re-factoring) Anyone can add to Product Backlog Product Owner is the only person that prioritizes Product Backlog Includes relative estimate of size of features (design, code, test, automate, refactor, doc, fix bugs)
- 31. Release Planning Communicate a common vision for the release Initial Design Align team on proposed functionality Determine target functionality for the release
- 32. Release Planning Groom User Stories small enough to be effective for sprint planning Determine the relative size of the user stories in story points Determine Release Functionality based on velocity Identify Dependencies
- 33. Sprint Backlog Tasks necessary to complete user stories Many-to-one relationship with user stories Coding, testing, automation, specs, doc, design, etc.
- 34. Sprint Backlog Team expands items on the Sprint Backlog into specific tasks, time estimates in hours, signs up for ownership Critical that “The Team” selects items and size for Sprint Backlog Managed through Scrumforce
- 35. Sprint Planning Determine the Sprint Goal Determine work necessary to complete the goal (with time estimates) Make commitments for the Sprint
- 36. Sprint Planning Meeting Team “dog piles” on user stories Team figures out how to deliver Sprint Goal even without a resource on the team who normally does a particular type of work Product Owner may negotiate but Team always determines what they can complete during the sprint
- 38. The standards by which we define "done" for sprint functionality is key to the success of iterative, incremental development. Functionality that meets these standards at the end of a sprint will be considered potentially release-able and demoed at the Sprint Review. Definition of “Done”
- 39. User Stories All defined Acceptance Criteria for a user story have been met. Code Code implementing the user story functionality is checked in and follows department standards . No open regressions (you break it, you own it), with automated tests written for all regressions. No open P1 & P2 bugs for the implemented functionality in the sprint. Quality Code Coverage of 70% Test plan, cases and execution for sprint functionality, regression and cross functional test cases related to sprint functionality, need to be 100% executed, and all P1/P2 cases passing. All resolved bugs have been verified and closed for the sprint functionality. Definition of “Done”
- 40. Performance/Scalability Performance/Scalability impact of sprint functionality understood and quantified, and systesting scheduled, if required, with the sys test team. User Experience UE reviewed new features or significant changes in the UI, feedback incorporated, all resulting P1 and P2 UI bugs fixed. Usability testing completed, feedback has been incorporated into the backlog. Localization All UI components have labels ready for localization vendors. Documentation User doc describing all aspects of sprint functionality complete / checked in. Definition of “Done”
- 41. Autobuild Page
- 42. Daily Standup Meeting: Pigs & Chickens Two types of people attend Daily Standup: Pigs and Chickens A chicken and pig were walking down the street. The chicken said to the pig, "lets open a restaurant." The pig said, "Ok, what should we name it." The chicken said, "How about "Bacon and Eggs"." The pig said, "No way … I'd be committed but you would only be involved ."
- 43. Daily Standup Meeting Re-connect, re-commit and share relevant information Team members answer 3 questions (in 2 minutes): What did you do yesterday? What will you do today? Are there any obstacles in your way?
- 44. Daily Standup Meeting 15 minutes or less All Pigs are required to attend Daily Standup Pigs talk. Chickens listen. Not a problem-solving meeting Obstacles are removed ASAP by the ScrumMaster
- 45. Burndown Charts Production support Resolution of dev assumptions Added Tasks Added March Tasks!
- 46. Sprint Review It’s all about feedback and visibility All teams demo done functionality to All Technology / Stakeholders Takes place after the last day of the Sprint
- 47. Sprint Review Only functionality that meets “Done” criteria is demoed Team declares what they committed to doing in the Sprint and did not get done Feedback from customers and stakeholders drives design changes for future sprints
- 48. Sprint Review User Story Doneness Checklist User documentation complete and checked in. All UI labels ready for localization vendors. Usability testing scheduled when necessary, and feedback incorporated into backlog. UE has reviewed any new features; P1 and P2 UI bugs fixed. Performance/scalability impact ascertained and sys testing scheduled if required. All resolved bugs verified and closed. 100% of test cases logged in QA Tracker and executed in a QA environment, and all P1/P2 cases passing. Code Coverage of 70% (or as agreed with team) No open P1 & P2 bugs No open regressions. Automated tests written and reviewed for all regressions. Code checked in and follows department standards. BT & Profile Perm Setup Page Handshake POC Done Criteria
- 49. Looks at “how” product is built (process, tools, etc.) Occurs after every Sprint What went well? What didn’t go well? What will you do differently next time? Retrospective