© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v. 7.6.2.

Slides:



Advertisements
Similar presentations
Project Name Kelly Waters July Author: Date: Version:
Advertisements

September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
How to Transfer from Waterfall to Iterative Te Bai, Ji Qi.
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
<<replace with Customer Logo>>
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
IBM Business Consulting Services © Copyright IBM Corporation 2006 Unified Process March 27, 2006 Chris Armstrong.
COMP 350: Object Oriented Analysis and Design Lecture 2
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Copyright Prosci All rights reserved. Library of Figures 1 Prosci Change Management ® Please read Right to use this content is governed by the licensing.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
UMT and Microsoft Presenting Tips and Tricks Basics What’s new in Microsoft Project 2010 Brian Feder, MBA, PMP Senior Vice President UMT Consulting Group.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
The Evergreen, Background, Methodology and IT Service Management Model
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
Using IBM Rational Unified Process for software maintenance
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1 Prosci ® Image Library. 2 Guidelines This library is not designed as a presentation, but rather a collection of available slides for potential use in.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Rational Unified Process Fundamentals Module 5: Implementing RUP.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Creative Disruption: A Core Systems Strategy Workshop November 3, 2011.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Introduction to Disciplined Agile Delivery (DAD) Scott W
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Replacing Your LMS: Why, When, What & How? When considering the viability of your LMS, it’s critical to deeply consider your organization and its needs.
Rational Unified Process Fundamentals Module 5: Implementing Rational Unified Process Rational Unified Process Fundamentals Module 5: Implementing Rational.
Info-Tech Research Group1 Info-Tech Research Group, Inc. is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
ServiceNow Special Interest Group Phased WorkTemplate Information & Educational Technology 1 DRAFT
Headline sample style Intro sample style Click to edit Master text styles –Second level Third level –Fourth level o Fifth level.
CLE Introduction to Agile Software Acquisition
Office 365 Security Assessment Workshop
Preliminary Power Point Slides
Identify the Risk of Not Doing BA
Assist Knowledge Development, Ltd.
Click to Add Title Click to Add Subtitle.
Information Technology Project Management – Fifth Edition
By: By: Agile Scrum Master Online Training.
Systems Analysis and Design in a Changing World, 6th Edition
Click to edit Master text styles
Who Wants to be a PMP? Pre-Course Game 3
Project Ideation Agile Down-to-Earth © 2016.
Author names here Author association names here
Click to edit Master text styles
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Click to edit Master text styles
Slide Title Edit Master text styles Second level Third level
ОПШТЕСТВО ТЕМА: МЕСТОТО ВО КОЕ ЖИВЕАМ Скопје
Author names here Author associations here
Author names here Author associations here
Employee engagement Delivery guide
Click to edit Master text styles
Appendix B Agile Methodologies
Author names here Author associations here
Click to edit Master text styles
Are you measuring what really counts?
Presentation transcript:

© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v

Agile Project Start © 2007 BigVisible Solutions, Inc.. All Rights Reserved 2 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Presentation Objectives Explore the typical agile project inception process Introduce the Inception/Program Deck

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 3 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment Activity Focus Activities are concurrent Activities begin as early as possible Roadmap highlights areas where specific activities are emphasized Inception artifacts represent a starting point – not an end point Artifacts mature throughout the project as knowledge and clarity is acquired

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 4 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap: Stakeholder Alignment and Program Initiation Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment key practices – 1-on-1 stakeholder meetings – agile intro sessions – stakeholder inception workshop(s) – program kick-off meeting stakeholder alignment goals: – identify stakeholders – define stakeholder roles – project consumer – project implementer – project dependency – org. stakeholder – align stakeholders on approach – define high-level goals and objectives – identify initial success measurements initiate program goals: – define program model – identify program participants – identify risks and dependencies – kick-off program artifacts – Project Deck – stakeholder roles – program and product vision – critical success factors – success measures – high-level program timeline – risk and dependencies – Program Model – participants – meeting frequency and logistics

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 5 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap: Team Formation and Training Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment objectives – identify team members – form team – define team principles – Ppovide basic training key practices – team workshops – foundational agile training classes artifacts – team manifesto or – team charter this is how we will work foundational training – Module 1: Agile Training Game (½ day) Objective: introduction to Agile – key agile concepts – Module 2: Agile Project Execution (½ day) Objective: explore agile project roles and practices – Module 3: Agile Estimation & Planning (½ day) Objective: learn key agile planning techniques

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 6 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap: Business Discovery Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment objectives – define baseline product vision – define features – define initial story backlog – size story backlog – identify risks – identify dependencies – define initial release plan key practices – vision brainstorming – model user/system flows – story workshops – sizing workshops – architectural discussion artifacts – product vision – release goals – release roadmap – feature list – prioritized, sized story backlog – risk/issues list

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 7 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap: Iteration 0 Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment objectives – prepare project environment – ready team – refine high-level architecture infrastructure – servers – continuous integration – environment setups – permissions tools – development tools – testing tools – apis – web services architecture – arch. workshops – development standards – system workflows – proof-of-concepts vendors – data vendors/feeds – licenses – SMEs training – tool training – process training – subject matter training

Agile Execution © 2007 BigVisible Solutions, Inc.. All Rights Reserved 8 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Project Inception Roadmap: Assessment and Evaluation Team Formation & Training Initiate Program Iteration 0 Assessment Business Discovery Identify Stakeholders Define Goals & Objectives Stakeholder Meetings and Alignment objectives – assess project readiness – evaluate Individual agile maturity and expertise – evaluate the Teams agile maturity and improvement individual assessment – objective : – evaluate team member agile progression – frequency – each iteration – tool : – Page-Jones Seven Levels of Expertise – individuals can score from Level 1 (innocent) to Level 7 (researcher/expert) – starting point: – individuals begin program at Level 1 or 2 – end goal: – team members should score a skill-level of 4 (practitioner) team assessment – objective – evaluate agile team maturity – frequency – each iteration – areas evaluated – release planning – iteration planning – process adoption – reporting – engineering practices – tool – team evaluation matrix

Agile Project Start © 2007 BigVisible Solutions, Inc.. All Rights Reserved 9 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Inception/Program Deck Output of Project Inception Process Living artifact – updated throughout project Program-focused rather than product-focused Represents snapshot of project/program May be customized to fit the program needs Purpose: Provide a single source of high-level program information Summarize program objectives and plans Outlines program stakeholders and participants Document dependencies, risks and trade-offs

Agile Project Start © 2007 BigVisible Solutions, Inc.. All Rights Reserved 10 ____ __ ____ _____ ____ ______ _____ _____ ____ _____ _____ _____ ____ _____ Click to edit Master text styles Second level Third level Fourth level Fifth level Inception/Program Deck: Contents Goals and objectives Program stakeholders, groups and participants Roles and responsibilities Program dependencies and risks Trade-offs Critical success factors Success measurement Release plans