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

Agile en Prince2

Agile en Prince2: bijt dat elkaar? Of vullen ze elkaar juist aan?
by

Paul Meek

on 10 August 2011

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile en Prince2

Double click anywhere & add an idea
Agile en Prince2
Populaire agile methoden en technieken

Scrum
Lean
XP
Kanban
Agile principes

Directe communicatie tussen ontwikkelaar en gebruiker
Sturen op business value
Korte iteraties
Simpele oplossingen
Wijzigingen horen erbij
Reflecteren en leren
Voortgang op basis van werkende software
Sustainable pace
elke dag
2-4 weken
2-12 weken
Rollen Prince2
Agile Information radiators
Prince2 Management Producten
Besturingsdimensies
Agile binnen PRINCE2
PRINCE2 principes
Continued business justification
Learn from experience
Defined roles and responsibilities
Manage by stages
Manage by exception
Focus on products
Tailor to suit the project environment
Business Case
Executive summary
Reasons
Business options
Expected benefits
Expected dis-benefits
Timescale
Costs
Investment appraisal
Major risks
Benefits Review Plan
Scope
Who's accountable
How and when to measure
Resources needed
Baseline measures
How to review performance
PID
Project definition
Project approach
Business case
Project management team structure
Role descriptions
Risk Management Strategy
Quality Management Strategy
Configuration Management Strategy
Communication Management Strategy
Project Plan
Project Controls
Tailoring PRINCE2
Plan
Description (level)
Plan prerequisites
External dependencies
Planning assumptions
Lessons incorporated
Monitoring and control
Budgets
Tolerances
Product descriptions
Schedule
Highlight Report
Date
Period
Status summary
This reporting period
Next reporting period
Project and stage tolerance status
Requests for change
Key issues and risks
Lessons report
Exception Report
Exception title
Cause of exception
Consequences of the deviation
Options
Recommendation
Lessons
End Stage Report
Project Manager's report
Review of the Business Case
Review of the project objectives
Review of stage objectives
Review of team performance
Review of products (handover)
Lessons Report
Issues and risks
Forecast
Business justification for initiating?
Necessary authorities exist for initiating?
Sufficient information available?
Project approach
Request to initiate the project
Reasons, benefits, risks
Clear scope and products to be delivered
How and when delivered - costs
Who's involved in decision making
How to achieve the quality required
How to control risks, issues and changes
How to monitor and control progress
Identification of stakeholders
How is PRINCE2 tailored for this project
Request to deliver a project
Assure that products from plan have been completed
Prepare the plan for the next stage
Update PID
Use the lessons learned
Request authorisation to approve next stage plan
Verify user acceptance
Ensure support
Review the project against its baselines
Assess benefits and plan review of benefits
Follow-on action recommendations
Principes Starting Up
Opstellen Project Brief
Software ontwikkeling complex en niet lineair: Methode Agile
Organisatie structuur
Principes Initiating
Kwartier maken voor ontwikkelteam
Chartering:
Mission en Business goals in BC
Product Backlog in PID
Project Roadmap (aanpak Architectural Baseline) in PID
Faseovergangen formele koppelmomenten naar Stuurgroep
Kwaliteit: In belangrijke mate bepaald door Product Owner
Fixed: Sprints (2wk)
Intentie: Release na x Sprints
Principe: Fase overgang altijd na Release. Tolerantie evt. 2 sprints
Principe: Voor einde fase altijd 1 sprint UAT
Principes besturing tijdens Stage
Workpackage is sprint
Retrospective bij Release
Lessons Log bij afronden Stage
End Stage Report bij afronden Stage
Periodieke update Stuurgroep dmv Highlight reports
Principe: Product Owner beslist of Release in productie gaat, eventueel via Request for Advice naar Stuurgroep
Architectural Baseline
Project Brief
Definition (background, objectives, desired outcome, scope and exclusions, constraints, tolerances, users and interested parties, interfaces)
Outline Business Case
Project Product Description
Project Approach
Project management team structure
Role descriptions
References
Methode Agile
Project Brief
Definition (background, objectives, desired outcome, scope and exclusions, constraints, tolerances, users and interested parties, interfaces)
Outline Business Case
Project Product Description
Project Approach
Project management team structure
Role descriptions
References
Previous Lessons
Sprint 0
infra
versiebeheer
ontwikkelomgeving
buildproces
continuous integration
OT(A(P))
Plan Stag1
Plan prerequisites
External dependencies
Planning assumptions
Lessons incorporated
Monitoring and control
Budgets
Tolerances
Product descriptions
Schedule
PID
Project definition
Project approach
Business case
Project management team structure
Role descriptions
Risk Management Strategy
Quality Management Strategy
Configuration Management Strategy
Communication Management Strategy
Project Plan
Project Controls
Tailoring PRINCE2
Tolerances:
- tijd: +- 2 sprints
- geld: +- 10%
- scope: variabel
- kwaliteit: Product Owner
Product Backlog
Product Backlog (stage 1)
Scrum board
Sprint Burnup
Daily Scrum
Sprint review
Sprint retrospective
Integraal testen tijdens Sprint
Mission & Business goals
Methode Agile
Versiebeheer
Releasemanagement
OTAP
Backup
Naamgeving
Rol Product Owner
Sprint review
Sprint retrospective
Extra test Sprint voor Release
TDD
Continuous Integration
Pairing
Integraal testen tijdens Sprint
User Stories
Sprint Planning
Sprint Backlog
Sprint Review (functioneel)
Sprint Retrospective (proces / techniek)
Highlight Report
Date
Period
Status summary
This reporting period
Next reporting period
Project and stage tolerance status
Requests for change
Key issues and risks
Lessons report
Input
Sprint Review
Sprint Retrospective
Sprint Burnup
Project Burnup
Checkpoint report
Niet van toepassing op Product Backlog
Sprint Retrospective
Sprint planning
Request for
Advice
Igv tegenstrijdige belangen bij
in productie nemen van release
Benefits Review Plan (update)
Scope
Who's accountable
How and when to measure
Resources needed
Baseline measures
How to review performance
End Stage Report
Project Manager's report
Review of the Business Case
Review of the project objectives
Review of stage objectives
Review of team performance
Review of products (handover)
Lessons Report
Issues and risks
Forecast
PID (update)
Project definition
Project approach
Business case
Project management team structure
Role descriptions
Risk Management Strategy
Quality Management Strategy
Configuration Management Strategy
Communication Management Strategy
Project Plan
Project Controls
Tailoring PRINCE2
Meetbare Benefits gerealiseerd
User / Maintenance Acceptance
Resultaat UAT
Tav volgende Stage
Relatie met Product Backlog
Update met actuals huidige Stage
Update met forecast volgende Stage
Product Backlog (stage 2)
Scrum board
Daily Scrum
Sprint review
Sprint retrospective
Integraal testen tijdens Sprint
Tolerances:
- tijd: +- 2 sprints
- geld: +- 10%
- scope: variabel
- kwaliteit: Product Owner
Product Backlog
Plan Stage2
Plan prerequisites
External dependencies
Planning assumptions
Lessons incorporated
Monitoring and control
Budgets
Tolerances
Product descriptions
Schedule
Project Roadmap
Feedback Cycles
Project Product Description
Title
Purpose
Composition
Derivation
Development Skills Required
Customer Quality Expect.
Acceptance Criteria
Project Level Qualit Tolerances
Acceptance method
Acceptance responsibilities
Project Product Description
Title
Purpose
Composition
Derivation
Development Skills Required
Customer Quality Expect.
Acceptance Criteria
Project Level Qualit Tolerances
Acceptance method
Acceptance responsibilities
Agile rollen
Product Owner
{
Startup
Initiatie
Beheersing
Risk management
Time ( to Market)
Functionality (Building the right thing)
Costs
Quality (Building the thing right)
Project
Chartering
Product Backlog
Project Roadmap
Project Burnup
Project Retrospective

Release
Project Roadmap

Sprint
Sprint Planning
Sprint Backlog
Sprint Burnup
Sprint Review
Sprint Retrospective

Daily Scrum
Internal blocker
External blocker

IP
IP - ?
IP - Project Plan
CS - Highlight Report
CP - Lessons Learned

SB - Stage Plan
MP (- Accepting Work Package)
MP (- Work Package)
MP - Checkpoint Report
MP - Delivering Work Package
CS - Issue List / Lessons Report

CS - Issue List
Issue Register
Sprint Retrospective
Blockers
Checkpoint
Report
(optioneel)
End Project
Report
Info uit de Project Retrospective
Verschillen PRINCE2 - Agile
Aansturing Workpackages - Zelfsturende teams
Project-stage-teamplan - Release-sprint-userstory-task
Sturen op eindproduct - Sturen op sprint
Change via stuurgroep - Change door Product Owner
Team-rollen - Team-expertises
Full transcript