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 20-25 (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 1 2 3 4 5
© 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
<<replace with Customer Logo>>
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
Software Development and Release Management By James Lawrence Software Development Manager.
Release and Iteration Planning September 13, 2008.
Trusted IT Group. The challenge: 40 active, concurrent IT projects Unsatisfactory Project Delivery.
> Blueprint Executive Summary >. Presentation Purpose; This Executive Summary captures the key details and outputs which merit stakeholder alignment to.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
The Business Analyst Role in Agile Projects
CASDA Project Management A presentation to the CASDA Preliminary Design Review IM&T / CASS Dan Miller | CASDA Project Manager 11 March 2014.
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
The Road to Agile From the Bottom Up Kevin Malley Tracey Clark 1 March 20 th, 2013 SWOQG.
WFO Planning Tool RFC & FCT
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
PDM-Project Delivery Methodology iDeaWORKS Journey from Good to Great Version: 1.0 Date: Feb 27, 2012.
User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD.
Agile/Scrum Case study Code name: ninja. 2 scrum teams One product backlog 8 months so far Long term project External integrations R&D and.
Scrum Jarred Payne Ashrith Pillarisetti. Scrum Prepare for Project Plan the Project Plan a Sprint Run a Sprint Track the Sprint.
Agile Lifecycle, Tools, Techniques IM Symposium.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
Software Quality Assurance Chip Ene, February 14, 2015.
Agile development By Sam Chamberlain. First a bit of history..
When is Agile the Best Project Management Method? Lana Tylka.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
Managing Software Development Projects with Jira.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
CHANGE CONTROL PROCESS SEPTEMBER 22, /16/2015 Purpose a methodical approach for capturing, managing and implementing IT changes ongoing management.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
User assignments (product owner) ‘circle’ 1 st sprint: ◦ Scrum Boards (informative workspace) Product -, release -, sprint -, defect backlog
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
SUPPORT THE WARFIGHTER MPE Reference Architecture Development Kick-off Meeting Deputy Director Architecture & Interoperability Office of the DoD CIO Thomas.
Software Testing Life Cycle
Sprint Review Results Example Template.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Essence Workshop June 20, Applying Essence in Practice Ed Seidewitz Ivar Jacobson International.
Introducing Project Management Update December 2011.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
© 2017 SlidePlayer.com Inc. All rights reserved.