Release Lifecycle Development Iterations / Start Here Next Release Re-estimate based on better granularity Customer UATGo / No Go for ReleaseAgree releaseDeploy.

Slides:



Advertisements
Similar presentations
Iteration Planning.
Advertisements

Walter Bodwell Planigle. An Introduction – Walter Bodwell First did agile at a startup in 1999 Got acquired by BMC in 2000 and spent the next 8 years.
> Sprint Planning Presentation API Release: Date: Presented by:
An open source QA stack testing tools for agile teams Presented by Aaron Evans
Proposal / Request For Proposal Proposal / Request For Proposal Initiation Control Planning Close-down Execution.
Maximize QA’s contribution to successful project deliveries Grace Shi, PMP, MBA, MEng Project Manager BCIT, Thurs Sept 25 th, 2008.
Agile Roadmap Prioritization Discussion. Agile Roadmap Prioritization: – Corporate Goals and Initiatives  Market Goals –Customer Feedback –Partner Input.
BAM! Business Analysis Methodologies. Change-driven or Plan-driven?
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
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.
C O N F I D E N T I A L 4-May-15 1 Attendee Management - Being Agile Attendee Management.
ESTIMATING Agile/practical project work TDT4290, NTNU, Trondheim Fredrik Bach 02/09/2014.
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
User Request BAU Prioritisation process Investment Prioritisation process PM BRD Stakeholders BA BRD Product Backlog Ranked list of requirements from BRD.
Implementation I - demo. Schedule * Project status -achieving the goals of the iteration -project metrics * Used work practices * Work results -presenting.
Agile development By Sam Chamberlain. First a bit of history..
GAI Proprietary Information
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Test Plan A document that indicates what testing will occur, how it will occur, and what resources will be necessary for it to occur. A test plan also.
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Scrum’s Product Owner Role Jeff Patton Agile Product Design
CSC444F'06Lecture 111 Process Control. CSC444F'06Lecture 112 The Process Document A document that concisely describes the steps we go through to produce.
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting July 14, Interactive Solutions Delivery Methodology What.
Roles in a Project Team By Sebastian Wagner And Michal Pieniazek.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Project Management Models
Team Skill 6: Building the Right System Managing Change (28)
© Mahindra Satyam 2009 Configuration Management QMS Training.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
CSC444F'06Lecture 101 Feature Tracking. CSC444F'06Lecture 102 Feature Tracking Keeping track of all the features that have been requested. Keeping track.
Extreme Programming Based on and
What Is DevOps? DevOps is "a portmanteau of 'development' and 'operations'" and is "a software development method that stresses communications, collaboration,
What Is Agile? Agile is a group of software development methodologies Scrum Extreme Programming (XP) Lean Etc. Key Characteristics: Small increments Adaptive.
Initiation Project Management Minder Chen, Ph.D. CSU Channel Islands
Meeting Practices Yan Wei Foundation Extreme programming is used Meeting practices are based on extreme programming technology with.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Successful Software Practice How to successfully work as a team to create software Chris Mendes, Chief Technology Officer Sirca Limited March 2012.
Extreme Software Engineering A Hands-On Approach From Extreme Software Engineering: A Hands-On Approach Daniel H. Steinberg Daniel W. Palmer.
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Agile = regular iterations, releases time-boxed incremental regular heartbeat streamlined collaboration co-located team on-site customer face-face communication.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
CMPS 116 Software Design Project. Introduction Instructor: Dr. Huahai Yang IBM Research – Almaden Former SUNY Albany Programming.
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
Agile development: a PM’s perspective
Project Management for Treasury Professionals
Change Request Management
SE503 Advanced Project Management
Testing Process Roman Yagodka ISS Test Leader.
Process Improvement With Roles and Responsibilities explained
Approaches to Systems Development
Change Assurance Dashboard
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Johanna Rothman Rank the Work Chapter 7
Development Lifecycle
Adaptive Product Development Process Framework
Reviewing Requirements and Capturing Questions
The Software Testing Life Cycle
Software Development In Agile
Software Development In Agile
Presentation transcript:

Release Lifecycle Development Iterations / Start Here Next Release Re-estimate based on better granularity Customer UATGo / No Go for ReleaseAgree releaseDeploy ReleaseHigh Level stories in story tracker Breakdown stories to estimable, consistent granularity Further analysis for candidate stories Decide candidates for release QACustomer IM PM Release Begins Final Testing for Release Customer IMPM BA Customer collaborates with Customer IMPM Dev Develop release (See Iteration Lifecycle) Prioritization of new requests Coordinate with Customer Dev Team Ongoing During Release Iterative Testing (New & Regression) Customer Showcases Get ready for next release Just in Time BA With support from Dev BA With support from IM QA

Iteration Lifecycle Development Iterations / Start Here Next Iteration Iteration Planning Meeting Customer Sign Off on Stories Change Requests Captured / Prioritized Develop IterationIteration Close and Retrospective Release Stories Identified, possibly in tentative iterations Story narratives written and signed off Breakdown stories further if needed Identify candidates for iteration IM Customer Iteration Begins Customer Showcase BA Customer Sign Off Test Iteration IM Story Tracking in tracker and story wall For all Customers Ongoing During Iteration Communication (PM level and Team level) QA Testing (New and Regression) Get ready for next iteration Just in Time Dev With input from BA Testers Dev BA With support from Customer Team BA supports Customers BA supports Customers Team

Story Lifecycle Development Iterations / Start Here Next Release In Play: Story re- estimated at IPM and in play for iteration Customer Signed off: Story functionality seen and approved In Regression Suite: Story covered in regression tests Dev Complete: Story functionality, dev tests, logging, etc complete Delivered: Story in Production Customer has a new request Ready to Play: Narrative written and signed off by customer Open: Story estimated, has customer priority & high level acc. criteria New: Story created but not yet valid (no acc. Criteria, etc) Showcased: Story showcased to customer BA Developer Signs Off Dev Machine Devs QA Signed Off: QA tests and approves story for showcase BA Customer supporting BA Customer working with Stories in the same story list should have similar granularities Narratives should be written JIT for next iteration/sprint Additional Notes Story prioritized for next iteration For all Customers Team BA supports Customers Deprecated: Story has been split or removed – no longer valid Customer BA Dev Devs Testers In simple projects, a narrative may not be necessary