We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAngelica Nugent
Modified over 2 years ago
> Sprint Planning Presentation API Release: Date: Presented by:
© 2013 Apigee Confidential – All Rights Reserved > This presentation should be used as a tool in the sprint planning meeting to review and obtain agreement on what will be accomplished by the team during the upcoming sprint. The goal is to have team members involved with decisions by interactively reviewing the backlog and discussing which user stories will be included in the upcoming sprint. The expected outcome of the backlog review is a sprint board with approved user stories that are ready to start on the agreed upon date. In order to accomplish this outcome, Apigees Scrum Master will need to drive the backlog review by using an online meeting tool to show the current backlog and the active build of the upcoming sprint board based on the teams discussion and feedback. 2 Purpose
© 2013 Apigee Confidential – All Rights Reserved Sprint Information 3 API Domains: Consumer/Internal Project Name: Sprint Overview: Include information such as theme of sprint, timeframe for sprint, internal deadlines driving sprint completion, etc Team Members: Project Manager Development Lead Technical Architect(s) Test team Customer Details Team Members: Scrum Master Development Lead Technical Architect(s) Test team Retrospective Review: Discuss top 3 retrospective items from previous sprint retrospective reviews to incorporate lessons learned into upcoming sprint Retrospective item 1: Retrospective item 2: Retrospective item 3: Provide review of overall program progress and highlight items to focus on given the teams current progress [i.e. required information for JIRA ticket before developer passes to test team, process to manage defects to resolution, etc.] Apigee Details
© 2013 Apigee Confidential – All Rights Reserved 4 Sprint Planning Agenda Backlog review to determine user stories in scope for upcoming sprint o Refer to active JIRA sprint board for review o Build upcoming sprint board during review Assumptions and Constraints Timeline o Team member capacity review Risks Communication Plan Questions
© 2013 Apigee Confidential – All Rights Reserved Backlog Review 5 At this point in the sprint planning meeting, Apigees scrum master will lead the backlog review directly in JIRA. The outcome will be a final list agreed upon by the team that includes all user stories, tasks, sub-tasks, QA tasks, feature requests, improvement requests, new features, and bugs that will be addressed during the upcoming sprint. >
© 2013 Apigee Confidential – All Rights Reserved Assumptions & Constraints 6 List all assumptions that apply to the upcoming sprint: [SAMPLE 1]: backlog includes all currently known and identified technical requirements Assumptions List all constraints that apply to the upcoming sprint: [SAMPLE 1]: sprint must be completed prior to internal customer deadline of June 1 Constraints
© 2013 Apigee Confidential – All Rights Reserved Sprint Timeline 7 MondayTuesdayWednesdayThursdayFriday 7-Oct8-Oct9-Oct10-Oct11-Oct Sprint Planning Configuration & Unit Test Configuration & Unit Test 14-Oct15-Oct16-Oct17-Oct18-Oct All Code moved to Stage QA Functional Test & Issue Resolution QA Functional Test & Issue Resolution Regression Test Performance Test Go / No Go Meeting Retrospective 21-Oct22-Oct23-Oct24-Oct25-Oct Deploy to Prod
© 2013 Apigee Confidential – All Rights Reserved Timeline Notes & Team Capacity 8 Address any notes applicable to the published timeline for the upcoming sprint: (examples below) Peer review to occur prior to deploying to Dev QA deploy to occur daily for completed tickets Code lock to occur on 9/9 Review of open tickets (if any) to occur on 9/9 prior to deployment to Stage: Finish in sprint Defer to next sprint Proceed with known defects in sprint Stage deploy will occur AM/Noon Monday Review of open tickets and issues to occur on Wed of GNG, similar decision criteria as noted above. Notes Team member capacity and impact to upcoming sprint: Team member 1 – PTO March (no impact) Team member 2 – PTO May 1-8 (shift open tickets to other available team member) Confirm capacity List any changes to capacity Team member capacity confirmation
© 2013 Apigee Confidential – All Rights Reserved Risks 9 Risk #Risk descriptionPotential ImpactMitigation PlanOwner
© 2013 Apigee Confidential – All Rights Reserved Kick-off meeting Daily scrum meetings Peer reviews daily prior to each deployment Grooming of sprint content (weekly meetings with Project manager and Scrum master) Dev planning sessions bi-weekly (ticket break downs/estimate quality) Evaluation on Mondays of dev completion if any items are not complete: – Finish in sprint – Defer to next sprint – Proceed with known defects in sprint Retrospective after sprint completion Communication Plan 10
© 2013 Apigee Confidential – All Rights Reserved Questions? Questions 11
Introduction to Scrum for Software Project Management Kevin Thompson, Ph.D. Project Management Professional Certified Scrum Practitioner Certified Scrum.
Sprint Review Results Example Template. License and Contact Details This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International.
Software Development QA Best Practices May 20, 2010 Suzette Hackl, CSM Senior Project Manager Skyline Technologies, Inc.
2 Welcome To Defect Management Training Objective: The objective of this course is to learn about standards that emphasize a best practice approach for.
Agile Lifecycle, Tools, Techniques IM Symposium.
Armstrong Process Group, Inc. Copyright © , Armstrong Process Group, Inc., and others All rights reserved Armstrong Process.
Microsoft Solutions Framework Executive Overview Microsofts Best Practices For IT Solutions Success Kyle Korzenowski Product Planner Microsoft Business.
Kathy Reed June 4, 2013 IIBA Austin CBAP Study Guide for the Business Analyst Body of Knowledge (BABOK) Version 2.0.
Metrics and Databases for Agile Software Development Projects David I. Heimann IEEE Boston Reliability Society April 14, 2010.
PHE 504 HEALTH PROMOTION FIELD EXPERIENCE – PRECEPTOR GUIDE Preceptor Orientation & Answers to Frequently Asked Questions.
Directions for this Template Use the Slide Master to make universal changes to the presentation, including inserting your organization’s logo –“View”
The Charter Partners ® Guide Effective Meeting Management Good meetings are managed events... they just dont happen! © Charter Partners USA, Inc. January.
My life as a Business Analyst - Presentation to IIBA Members By: Scott A. Mackay.
Project Management in Team Software Projects The primary challenge of project management is to achieve all of the goals of the project charter while adhering.
1 Test documentation and Test case design Iana Mourza QA Lead/Release Lead VMware, Inc
Ch-10 Configuration Management. Introduction A software project produces a number of items during its execution including various documents, manuals,
UNIT-V DEFECT PREVENTION 1Defect prevention (Arun)
Review Planning meeting for project name. © Local Partnerships LLP 2009 Time Add start and finish Welcome/introductions of review team Purpose of meeting.
Chapter - 5 Understanding Requirements Unit II. Introduction Definition : “The broad spectrum of tasks and techniques that lead to an understanding of.
The Business Of Working With IT Moderator: Rick Treese, Advanstar Panel: Thomas Falconer, Source Media Ken Hoffman, Standard & Poors Investment Services.
Adult Protective Services System (APSS) Project Progress Report Prepared by: APSS Project Team Date: September 16, 2008.
Review planning meeting for Name Surname Job Title.
Project Proposal William Chow, Amer Al-Mousa, Osama Mohammed 1.
Presented to By. 2Normative references ISO 9000:2005, Quality management systems Fundamentals and vocabulary ISO 19011:2002, Guidelines for quality and/or.
This presentation, including any supporting materials, is owned by Gartner, Inc. and/or its affiliates and is for the sole use of the intended Gartner.
The world leader in serving science Managing Change in an ISO/IEC Environment Kelly Huckabone, MLT, ASQ, CQIA.
Copyright © , Armstrong Process Group, Inc., and others All rights reserved Made available under EPL v1.01 Project Management Review Eclipse Process.
UR Financials Project Demo Days April UR Financials Demo Days – April 2014 Agenda Project Update and Delay Details Impact to Project Deliverables.
© 2016 SlidePlayer.com Inc. All rights reserved.