Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.

Slides:



Advertisements
Similar presentations
Behavior Driven Test Development
Advertisements

Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Iteration Planning.
> Sprint Planning Presentation API Release: Date: Presented by:
©2011 Improving Enterprises, Inc. Breaking down the Epic User Story.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Agile at ON.Lab Bill Snow VP of Engineering. What is waterfall? RequirementsDesignDevelopTest Or Requirements Design Develop Test Time.
Local Touch – Global Reach The New Tester Matthew Eakin, Manager Managed Testing Practice Sogeti, USA.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
NAUG NAUG Knowledge Evening – th February 2007.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
The Business Analyst Role in Agile Projects
Atlassian Africa South Africa 2015 Jonathan Singh.
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
Managing a Project Using an Agile Approach and the PMBOK® Guide
The Product Owner prioritizes the requirements or features through feedback from the Stakeholders & interaction with the core team The Team.
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.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Adopting Agile for Enterprise Software Joe Bedell, Software Engineer Jason Breen, Software Engineer Peter Melko, Scrum Master June 15 th, 2015.
Software Development Landscape
What is Scrum Process? Where is it used? How is it better?
Agile Adoption GMAS Product / Practice Teams PMO Meeting – May 2014.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Information Development Projects
©2011 Improving Enterprises, Inc. Epics and Agile Planning.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Dana LaRieal Morales, PMP
Theories of Agile, Fails of Security Daniel Liber CyberArk.
January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.
Cultivating Agile Requirements
CDU – School of Information Technology HIT241 Integration Management - Slide 1 HIT241 - Project Integration Management Introduction Project Integration.
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Text Firefox Metro Project Production Pipeline. Text Our Approach.
Who is Gregg? 1 Mile
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
CSE Senior Design II Scrum Review/Discussion Instructor: Mike O’Dell.
Agile Project. Agile - Project proj·ect präj ˌ ekt noun an individual or collaborative enterprise that is carefully planned and designed to achieve a.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Agile Project Management
Project Management with VSTS
Scrum.
Scrum and TargetProcess
Waterfall, Agile & Scaling Agile
Agile Training – Agile Overview
Agile Scrum Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
By: By: Agile Scrum Master Online Training.
Scaled Agile Requirements: What, When & How
Product Backlog List of things that needs to be done to make the product come into existence 
Chapter 3: The Project Management Process Groups: A Case Study
CEN 4010 Intro to Software Engineering Professor Alex Roque
Sample Agile Assessment Report for XYZ Company
Fast, Agile, Simple Decemebr 2017 Think Simple, Run Faster.
Summarizing Our Models to Date
SUCCESS MANTRAS FOR BEING AN EFFECTIVE INFORMATION DEVELOPER IN AGILE
Localize implementation to best meet Value Stream Goals
Sprint Planning April 2018.
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Software Development In Agile
Scrum in Action.
Sprints.
Are you measuring what really counts?
Software Development In Agile
Presentation transcript:

Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com

Agenda Emergence Tech Training / emergencetechtraining;com What is Release Planning? When does it happen? Team Roles and Responsibilities Using Jira to manage Release Planning  Managing your backlog  Managing Sprints  Closing the Sprint

What is Release Planning? Emergence Tech Training / emergencetechtraining;com In an Agile world release planning provides visibility to upcoming work. Effective release planning provides the team with an ability to work in small increments, enabling strong focus and high quality work. Release Planning in a Nutshell is:  Building a Product Backlog – Shared Knowledge  Prioritizing the Backlog – Project Plan  Continue to ‘groom’ the Backlog – Manage Scope  Execute on the Backlog – Build your Product

What is Release Planning Emergence Tech Training / emergencetechtraining;com An ability to derive a project schedule based upon:  Total number of Story Points for a particular project or product feature  A Scrum Teams historical velocity  Assumes that the team has been together for awhile  If team is new Risk is associated with the Release Plan until such time as the team velocity hits the estimated velocity. What is Velocity?:  The Total number of points that a team can complete within a designated Sprint. Why is Velocity Important?  Provides predictability.

When Does it Happen? Emergence Tech Training / emergencetechtraining;com Release Planning happens throughout the project. Pre-Sprint Planning:  Build the Product Backlog  Estimate Story points to the Stories in the backlog  Prioritize work based upon highest value first  Set project milestones and expectations via Planning

Team Roles and Responsibilities Emergence Tech Training / emergencetechtraining;com Getting to Release Planning:  Discovery – Collaborative effort to build out individual User Stories and Acceptance Criteria.  Building Context for your Product/Features.  Who? – The entire team  Estimation – Story Point stories that are going to be included in the development phase of the project.  Who? – The entire team  How – Team needs to decide if they will estimate collectively or separately with respect to Dev and QA efforts.  Release Planning:  Prioritizing the User Stories  Who? – Primarily the Product Manager, with input from the the rest of the team.