Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

My Project Management Framework

No description
by

Colart Miles

on 17 July 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of My Project Management Framework

Agile Project Management
Project as a Vehicle?
Project Lifecyle
Project Steerage
Tools & Techniques
"Managing The context"
Pilot
Engine
Fuel
Plan
Engineered to deal with conditions
Starting Point
Destination
Map/path
Trials & tribulations
Airplane?
Journeys
You can't predict everything though...
So build it to manoeuver
97%
The amount of time spent 'off course' to the moon. Continuous Course Correction
Product Focus
Project Focus
Project Anatomy
Project Assets
Business Case
Project Charter
Roadmap
Status reports
Budget
Comms Plan
Benefits plan
Project Activities
Idea Stage
Scoping
Cost estimation
Benefits estimation
Highlevel approach/roadmap
+/- 40% certainty factor
Pre-flight Stage
Scope refinement
Success criteria
Risks & Issues
Costs & Benefits
Roadmap refinement
Stakeholder analysis (winners & losers?)
Quality agreement?
+/- 10% certainty factor (with assumptions)
In-flight Stage
Plan
Project Initiation
Regular 'Check & Adjust'
Updating the 'plan' (refining the roadmap)
Project Status (time, budget, quality)
Communications Plan
Escalate early & often
Project Roles
Post-flight Stage Plan of Attack Review
Formal Project Closure
Resources released
Handover to BAU
Benefits review scheduled
Activity Based Planning
9 PM Commandments
Project Planning
Financials
Managing Risk
Measuring Progress
Plan the flight then fly the plan.
The worst time to define success is after it's over!
2. Manage by result, not activity
Burndown Charts
Estimation Concepts
Understand Technical Debt
Focus on Throughput...

An active team is not the same as a productive team!
Project Manager
Product Manager
Project Sponsor
Delivery Team
Air Traffic Controller
Bat & Cash
Vision
Responsible for benefits realisation
Manages the >>content<<
Feature & Release
Technical
Deliverables Focussed
Manages the <<context>>
Facilitates and enables delivery
Business Case focussed
Turns the lights green
Implementors
Respected Experts
Prime source of estimates
Delivery focussed
Idea Checklist
In-Flight Monitoring
Project Business Case
+/-10%
Costs & Benefits?
Risks?
Assumptions?
Project charter (Flight plan)
Clearance?
Idea Brief
+/- 40% estimates
Costs & Benefits?
Risks?
Landing
Blindspots covered?
Early warning systems?
Stage Priming? (e.g. marketing, testing)
Rapid Response & Decision making
Situational awareness!
In-flight Retrospectives
Manage tensions (time, budget, resources, scope, quality)
Release the team & Resources
Gather evidence of delivery (success criteria)
Formal sign-off?
Project Governace
Pre-flight Checklist
inspired by Opportunities...
or issues
Broad guesses
Art of the possible
Pre-flight
In-Flight
Post-Flight
Are we sure we wanna do this?
How will we know we're done?
What could go wrong?
What could go right?
What's the opportunity cost?
Who should be involved?
What do they need?
Product in support
Opportunity to learn
Was it successful?
Start doing, stop doing, keep doing
Idea Phase
Analysis Mode
Design Mode
Build Mode
Test Mode
Rollout Mode
Requirements
Feature Ideas
Issues/bugs
Don't know what the answer is but here's the question...
SOLUTION NEUTRAL!!
Solutions?
Feature Specs
Design Decisions
Here's how we're going to meet the requirements...
Coding
Documenting
Testing
Estimations
Challenge Assumptions!

Prove it won't work!!
Public, Private & Invitation Beta's
Designing experiments!
Evidence Based
Find bugs early & cheap ...instead of late & expensive!

Marketing
Coordination with Partners
Handover to Support
Documentation (manuals, wiki etc.)
Business As Usual
Stakeholders
VOC: Voice of the Customer
MOT: Moment Of Truth
Cover Blindspots
Respected Experts
Prime source of Situational Information!
Air Traffic Control
Are we sure we wanna do this?
How will we know we're done?
What could go wrong?
What could go right?
What's the opportunity cost?
Who should be involved?
What do they need?
Pre-flight
Post-Flight
inspired by Opportunities...
or issues
Broad guesses
Art of the possible
Idea Phase
Product in support
Opportunity to learn
Was it successful?
Start doing, stop doing, keep doing
In-Flight
Take-off!
Planning Session involving all stakeholders
Success Criteria Defined at start
Quality statement
Serato Project Business Case
Risks?
Assumptions?
Serato Plan of Attack (Flight plan)
Clearance?

Continuous Course Correction

Evasive Manouvers
Escalate early and often (status reports? conversations?)
Anything affecting the probability of success!
Beware of the "false dichotomy"
Examine alternatives
Check Side-effects? (Make sure you don't multiply problems)
Be decisive!

Dont react.... Respond!!
Comms!!!
Keeping everyone informed.
Single source of information.
Dashboard model (Wiki? rss?)
Multiple audiences: Marketing, management, dev, support, partners, consumers, QA.
VOC: Voice of the customer?
Stage Priming? (e.g. marketing, testing or support)
3. Compromise on Scope not Quality!
4. Escalate early & often
5. Continuous Course Correction
1. Begin with the end in mind
6. Serve your team
7. Manage the context
Stakeholders!
8. DWYSYWDWYSYWD
Do What You Said You Would Do When You Said You Would Do It!!
Maintain situational awareness
9. Retire Risk Early!
Tiger Cubs... versus Tigers!
The act of planning is more valuable than the plan!
Enable & facilitate
Product
^
A
B
C
D
E
F
B
C
F
A
E
D
Monitor Status Reports
Escalation Point
Gauge probability of success (should increase over time)
Only intervene as a last resort
Project Sponser Powers?
Money, Scope, Resources, Tiumescales, Partner Relations
On sale?
In Support (operationalised)?
Resources released?
Technical Debt?
Total Cost Ownership? (Impacts)
Benefit Realisation Plan?
Formal Closure Checklist
Impact on Sales?
Operational impacts (support, comms, side effects?)
Risk exposure?
Brand equity?
Staff satisfaction?
Benefits Realisation
Regularly Poll Priority
2 x 2 x 2 escalation...
2 minutes to explain the problem
2 minutes to describe some options
2 minutes to make a decision
Communicate little bits of news... often!
Leave the gardening to the gardeners!
Test Driven Development?
Stay wedded to the outcome not the path to get there!
Deliberate & Presciptive
Emergent & Adaptive
KanBan
No PM
Scrum
RAD/ XP/ Others
Waterfall (SDLC)
Right vehicle for the job?
Follow a prescibed process
Deal with changes as they happen
High inertia
Low variety
Tame problem space
No concept of work unit

Small unit of work (e.g. feature task)
Lightwieght PM framework
Visualise the workflow
Limited Work-in-Progress
Measure the lead-time
Throughput focus
Little or no PM needed
Self managed (little or no PM)
Small unit of work (e.g. feature task)
Self organised teams
Product Backlog prioritised and estimated for relative effort
Defined Sprints
Retrospectives
Optimised releases (Product Backlog managed by a product owner)
Integration testing
Just-in-time analysis
Prototyping
TDD
Continuous integration
Shared resources
Iterative
SDLC spiral
Analysis, Design, Build, Test, Rollout
Anticipate everything upfront
Gantt chart view of project
Sequential SDLC
Single Unit of Work
Heavy weight
Little room to adapt
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Planned versus Actual
VOC: Voice of the Customer!
Content
Context
Tech Experts
Engine room
Creative Problem Solving
Source of problems
Opportunities
Issues
Threats
Incidents
Expectations
Demands
Environmental factors
Full transcript