© 2008, Rasmusson Software Consulting, All rights reserved Your project is already dead. You just dont know it. Jonathan Rasmusson.

Slides:



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

© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Best Practices for an ECM Strategy
Agile Samurai Principles. Agile Development Deliver Value Every Iteration Break big problems into smaller ones Focus on most important issues Deliver.
<<replace with Customer Logo>>
ESTIMATING Agile/practical project work TDT4290, NTNU, Trondheim Fredrik Bach 02/09/2014.
Agile Planning. The problem with documentation Argument: “Heavy” documentation too much for most business-style projects.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Lecture: Requirements Development - Vision and Scope.
Entrepreneurship I Class #8 VOSG I Business Plan and Finances.
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
Chapter 3: The Project Management Process Groups
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Change Request Management
Product Management 1. The Product Champion  Nearly every successful project has a Product Champion who: Develops the Vision Document. Manages customer.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Greater Profits and Business Value
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
Software Development Landscape
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Copyright David Churchville - XP and Agile Planning David Churchville ExtremePlanner Software XP Fishbowl.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Tim Dean Art Director Central Media Microsoft Game Studios.
04 | Define a Software Iteration Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Jeffrey Murray Test Manager PowerPoint Microsoft Silicon Valley.
1 Planning – Agile Style Highsmith, Ch 7 All kinds of iterations! CSSE579 Session 3 Part 1.
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.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Using the Right Method to Collect Information IW233 Amanda Murphy.
University of Southern California Center for Systems and Software Engineering Agile Project Management Tools Supannika Koolmanojwong CSCI 577a.
The Agile Inception Deck
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Product Management Or.. The most important thing most startups forget to do.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting March 3, Gathering Requirements On an Agile Project…
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
Outlines Overview Defining the Vision Through Business Requirements
Project Management Enabling Quality Marien de Wilde, PMP April 2007.
CHANGE READINESS ASSESSMENT Measuring stakeholder engagement and attitude to change.
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
How Project Management Tool Helps Sticking To Basic Project Management Principles  Organizations can consider using project management tool to facilitate.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Workshop 4: Developing a one page business case
Change Request Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
COMP8040 – Cloud Application Frameworks Agile Project Management
Pragmatics 4 Hours.
EI Architecture Overview/Current Assessment/Technical Architecture
Managing the Project Lifecycle
Fundamentals of Information Systems, Sixth Edition
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.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Process Improvement With Roles and Responsibilities explained
Chapter 3: The Project Management Process Groups: A Case Study
How does a Requirements Package Vary from Project to Project?
By Jeff Burklo, Director
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
The Agile Inception Deck
Software Development In Agile
Adapting Agile in Pharmaceutical Industries
Software Development In Agile
WORKSHOP Establish a Communication and Training Plan
Presentation transcript:

© 2008, Rasmusson Software Consulting, All rights reserved Your project is already dead. You just dont know it. Jonathan Rasmusson

© 2008, Rasmusson Software Consulting, All rights reserved A few words for our sponsors

© 2008, Rasmusson Software Consulting, All rights reserved Your project is already dead. You just dont know it. Jonathan Rasmusson

© 2008, Rasmusson Software Consulting, All rights reserved Setting the stage You can be doing everything right, and still fail.

© 2008, Rasmusson Software Consulting, All rights reserved

Inception Deck Purpose Designed to: –Eliminate confusion and misunderstanding about what this project is about –Shine a big spot light on areas of potential conflict and misalignment –Highlight challenges BEFORE the project begins –Are we all in agreement? * Original Inception deck created by Robin Gibson of ThoughtWorks, based on the work of Rob Thomsett (Radical Project Management)

© 2008, Rasmusson Software Consulting, All rights reserved 1. Remind ourselves why we are here

© 2008, Rasmusson Software Consulting, All rights reserved Review stakeholder objectives Departmental objectives –Reduce number of support calls by 20% –Increase market share –Support business –Share knowledge Empathize, learn and understand whats driving your stakeholders

© 2008, Rasmusson Software Consulting, All rights reserved 2. Create an Elevator Pitch For [target customer] who [statement of the need or opportunity] the [product name] is a [product category] that [key benefit, compelling reason to buy] unlike [primary competitive alternative] our product [statement of primary differentiation].

© 2008, Rasmusson Software Consulting, All rights reserved Example - Silicon Graphics For [post production film engineers] who [are dissatisfied with the limitations of traditional film editors] the [SGI workstation] is a [digital film editor] that [lets you modify film images any way you choose]. Unlike [workstations from Sun, HP, or IBM] our product [has all the interfaces needed for post-production film editing].

© 2008, Rasmusson Software Consulting, All rights reserved Example - Quicken For [the bill-paying member of the family] who [is tired of filling out the same old checks] the [computer program Quicken] is a [PC home finance program] that [automatically creates and tracks all your check-writing]. Unlike [Managing you Money] our product [is optimized specifically for home bill-paying].

© 2008, Rasmusson Software Consulting, All rights reserved Whats cool about magazines? They hook you at a glance Make their product compelling Show benefits –Not features

© 2008, Rasmusson Software Consulting, All rights reserved Features dont sell – benefits do FeatureBenefit 245 Hp Engine Anti-lock breaks Cruise control Pass safely on the highway Brake safely with loved ones Save $$$

© 2008, Rasmusson Software Consulting, All rights reserved 3. Design a cereal box – sell your product!

© 2008, Rasmusson Software Consulting, All rights reserved 4. Create a NOT list

© 2008, Rasmusson Software Consulting, All rights reserved Objectives and Scope ISIS NOT (but could be) [In scope project objectives here][Out of scope project objectives here] UNRESOLVED [Unresolved project objectives here]

© 2008, Rasmusson Software Consulting, All rights reserved 5. Meet your neighbor(s)

© 2008, Rasmusson Software Consulting, All rights reserved Organizational Context External Entities Entity 1 The Application Functional area 1 Functional area n Entity n Business Entities Entity 1 Entity n IT Entities Entity 1 Entity n

© 2008, Rasmusson Software Consulting, All rights reserved 6. Map the terrain

© 2008, Rasmusson Software Consulting, All rights reserved Users Existing Systems Other initiatives External Systems Logical Scope Operations Support Out of Scope In Scope Legacy Mainframe App DB Enterprise Bus (SOA) Accounting Reporting The Application Functional area 1 Functional area n 3 rd Party DB Message Queue

© 2008, Rasmusson Software Consulting, All rights reserved 7. Design the blueprints

© 2008, Rasmusson Software Consulting, All rights reserved Services Technical Vision SQL Server Mainframe ELT Trans. Thin Client Databases DB 1 DB 2 DB N Transform. Layer Batch All trades Apollo Customer Main Page Client-side Security Validation Web Services Create New Update existing Search by Id Remove Domain Logic Accounts Ledgers Trades Data Access Layer 3 rd Party Tools Complex Calcs 3 rd Party Tools NHibernate Database Content DB Hercules Message Queue Pending Orders updates listens Order clearing house

© 2008, Rasmusson Software Consulting, All rights reserved 8. Ask what keeps us up at night?

© 2008, Rasmusson Software Consulting, All rights reserved Ask tough questions Beginning of project End

© 2008, Rasmusson Software Consulting, All rights reserved High-Level Risks What could go wrong? –Is there anything we can do about it? Eliminate what you can –Technical spikes / prototype Then move on Dont get hung-up (awareness)

© 2008, Rasmusson Software Consulting, All rights reserved Remember the Lords Serenity Prayer Grant me the serenity to accept the things I cannot change, The Courage to change the things I can, And the wisdom to know the difference. - The Serenity prayer

© 2008, Rasmusson Software Consulting, All rights reserved 9. Size it up 3 months 6 months 9 months Story gathering / estimation / prioritization

© 2008, Rasmusson Software Consulting, All rights reserved What will it take - Project Staffing #RoleCompetencies 1Project ManagerSolid Agile Project Management experience Financial services experience a plus 6DevelopersJ2EE/STRUTS/ANT Infrastructure set-up (CC, Functional testing) 2AnalystsXP-style Story Cards (testable, traceable, etc) Test script creation Iterative analysis experience 1CustomerAble to make decisions Source of truth 1QAAutomated Testing expertise

© 2008, Rasmusson Software Consulting, All rights reserved 10. Clarify whos calling the shots? The Golden Rule

© 2008, Rasmusson Software Consulting, All rights reserved Management Structure

© 2008, Rasmusson Software Consulting, All rights reserved 11. Trade-Off Sliders Feature completeness Stay within budget Deliver the project on time High quality, low defects Increase profitability by 10% Make business ecstatic Delight customers ONOFF ONOFF ONOFF ONOFF ONOFF ONOFF ONOFF

© 2008, Rasmusson Software Consulting, All rights reserved Project Estimates Internal Release 0.5 Estimates: –12 weeks staffed as follows - Xxx Remainder of Release 1 guesstimated at 9 weeks Remaining releases guessed – via extrapolation from Story count – at 46 weeks These numbers will be reassessed following Iteration 2, IR 0.5 and R1

© 2008, Rasmusson Software Consulting, All rights reserved Go or no go

© 2008, Rasmusson Software Consulting, All rights reserved What do we need to pull this off? 2 weeks Whole team –Stakeholder –Developers –Analysts –PM –QA Stakeholder time is critical!

© 2008, Rasmusson Software Consulting, All rights reserved What if I cant get stakeholder(s) time?

© 2008, Rasmusson Software Consulting, All rights reserved Key things to remember Set peoples expectations early –Be clear on time commitment –Use mornings for discussion –Afternoons for offline refinement Demand stakeholder involvement Be flexible Certain exercises wont finish in time allocated (you will need to iterate)

© 2008, Rasmusson Software Consulting, All rights reserved The end

© 2008, Rasmusson Software Consulting, All rights reserved Apologies - Shameless plug

© 2008, Rasmusson Software Consulting, All rights reserved Agile Project Management Training Agile Intro Agile Project Inception Fundamentals Roles and Responsibilities Team Practices Iteration Planning Building the first plan Story gathering Estimation/Prioritization The first plan Iteration Mechanics Analysis / Dev / Test Sync Points Tracking Velocity Big visible charts Status reports Retrospections Wrap-up Transition Support

© 2008, Rasmusson Software Consulting, All rights reserved