Day 1 Big Room Planning 8:00 - 9:00

Slides:



Advertisements
Similar presentations
Lean Startup Presented by:
Advertisements

Iteration Planning.
Agile Roadmap Prioritization Discussion. Agile Roadmap Prioritization: – Corporate Goals and Initiatives  Market Goals –Customer Feedback –Partner Input.
An Agile Retrospective Clinton Keith Overview Retrospective format What works (clear wins)? What doesn’t work so well? What do we need to start doing?
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
© 2009 Leffingwell, LLC Agile Enterprise Release Planning.
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
©2013 Scaling Agile With SAFe August 13, 2013.
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.
 User assignments (product owner)  ‘circle’  1 st sprint: ◦ Scrum Boards (informative workspace)  Product -, release -, sprint -, defect backlog 
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering.
Programming with eyes wide open. Your host today Subby Angelov Team
May 2013 Resources & References on Agile Methodologies Health System Portfolio Management Agile Workgroup/Strategic Investment Management.
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.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
© 2009 Leffingwell, LLC. Appropriate graphic goes here A Lean|Agile Learning Journey for Nokia S30/40 Managers Module 6: Implementing the Agile Release.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting July 14, Interactive Solutions Delivery Methodology What.
Definition of Ready: An Experience Report from Teams at Cisco XP 2014 學號 : 學生 : 鄭博仁.
1 Agile Release Management. 2 Recall - Highsmith’s remedies for schedule risk Team involvement in planning and estimating Early feedback on delivery velocity.
XP Overview Short Life cycle Risky / Dynamic Requirements Increase developer productivity.
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.
April 24, 2017 Agile BVIR.
Planning for Success (aka “Avoiding Failure”) Project Planning 1.
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Extreme Programming Based on and
January 24, 2009 Agile Product Management Making Things Happen Walter Bodwell Planigle.
Project management methodologies Waterfall vs. agile vs. half-arsed agile.
NAPA Agile Story: From Zero to Hero in Two Years Toivo agilehope.blogspot.com #NAPA #SAFe.
Agile Project. Agile - Project proj·ect präj ˌ ekt noun an individual or collaborative enterprise that is carefully planned and designed to achieve a.
Strategy Mapping Clear path to a successful Agile strategy Dave Neuman Sep 24, 2015 LinkedIn:
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Manifesto for Agile Software Development
Project Management with VSTS
Agile Training Day 2 November 17, 2015.
Agile Software Development II
Agile Scrum Management
Agile Frameworks Individuals and interactions over processes and tools
September 20, 2017 Agile Techniques Workshop Susan Futey
Agile Software Development Brian Moseley.
By: By: Agile Scrum Master Online Training.
Scaled Agile Hot Topics
Creating User Documentation in an Agile World
Project & Program Governance
Supannika Koolmanojwong
Chapter 3: The Project Management Process Groups: A Case Study
Waterfall and Agile Quality Techniques
Agile Development and the Scaled Agile Framework
Sample Project Portfolio
Fast, Agile, Simple Decemebr 2017 Think Simple, Run Faster.
What do you need to know about XP?
Johanna Rothman Agile Team Measurements Chapter 12
Resources & References on Agile Methodologies
Project Ideation Agile Down-to-Earth © 2016.
Epic Roadmap July-Dec 2019 Non Linux Platform Support July-Dec 2018
Requirement Management Automation with Atlassian Stack
Scaled Agile Frameworks
Agile Development.
Evolving a Continuous Improvement System
Product Development & Planning
Presentation transcript:

Day 1 Big Room Planning 8:00 - 9:00 Roadmap Portfolio and Epic Roadmap Overview Program Portfolio Leadership Presents 9:00 - 10:30 Feature Roadmap, Prioritized Business and Tech Features, Architecture Pres. Product Manager & Leads/Arch Presents 10:30 - 11:00 Lean | Agile Team Planning Guidelines Agile Program Manager Presents 11:00 - 4:00 Team breakouts (Lunch will be served) Lean | Agile Teams Develop Delivery Plans and Identify Risks & Dependencies Product Managers, Leads & Architects Circulate 5:00 - 6:00 Delivery Plan Reviews and Feedback Leadership, Product Managers, Leads & Architects Reviews Delivery Plans and Provide Feedback

Day 2 Big Room Planning 8:00 - 12:00 Delivery Plan Revisions Lean | Agile Teams Finalizes Develop Delivery Plans, Risks, & Dependencies Product Management, Leads and Architects Circulates to Provide Support 12:00 - 1:30 Final Delivery Plan Presentation & Lunch Lean | Agile Teams Present Final Delivery Plans 1:30 – 4:00 Review Risks & Dependencies Categorize Risks & Review Ownership of Dependencies 4:00 - 4:15 Commitment Confidence Lean | Agile Teams Confidence Vote 4:15 – 5:00 Retrospective Survey & Discussion Survey Discuss Feedback

Lean | Agile Team Delivery Plan User Stories Spikes Defects Technical Stories Risks U1 U2 S1 U6 T1 U3 U5 T2 U4 Iteration 1 Velocity : U1 S1 U2 D2 U3 D1 U5 U6 U4 Iteration 2 Velocity : U1 S1 U2 T1 U3 D1 U5 U6 U4 Iteration 3 Velocity : U1 S1 U2 D1 U3 T1 U5 U6 U4 Iteration 4 Velocity : U1 U2 D1 U6 T1 U3 U5 D2 U4 Iteration 5 Velocity : U1 T1 U2 S1 U3 D1 U5 U6 U4 Iteration 6 Velocity : Goals Goal 1 Goal 2 Goal 3 Goal 4 Goal 5 Goal 6 R1 R2 R6 R3 R5 R7 R8 Risks

Program Portfolio Dependency Board Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6 Milestones/ Releases Scrum Team 1 Scrum Team 2 Scrumban Team 3 Kanban Team 4 Kanban Team 5 XP Team 6 XP Team 7 External Features Inter-Team Dependency Milestone/Release

Frequency and Impact Graph Treat Terminate Tolerate Transfer Risk 1 Risk 5 Risk 2 Risk 4 Risk 3 Impact Frequency