Project Planning and organisation
1.0
What is a Project? Reach a defined goal With limited resources Within a fixed time
Planning To think about: What are we supposed to achieve? How do we get there?
Too little planning No unified picture of what should be done Great risk to deliver the wrong thing Time is lost on rework Frustration of not having control of the situation Badwill, usually the client discovers that something is wrong
Too much planning You never get closer to the goal Increased risk that taget is moving Constant re-planning Never get to know the system Everyone gets frustrated by not getting to work
What is the right planning?
Some useful tools Mile stone plan Responsibility matrix Customer interaction tools Risk analysis
Milestone plan
10 When the system architecture description is approved by Product owner and System architect
A good milestone plan Helicopter view State oriented, what not how milestones Find soul of the project i.e. what is special (difficult / risky) in this particular project? Promotes communication internal/external Suitable MS candidates: external events, big risks (difficult things, not done in the past), natural deliverables
Responsibility matrix Role Task Resp Task Resp Task
Legend R= Responsible (incl. execution) E=Executes D=Makes decision I=Should be informed A=Advisor
Responsibility matrix CTOSystem Architect Product owner System Architecture IRD
Roles that tend to lead to success Project manager System architect Client nagger Integration responsible Test responsible CM responsible Team leads (scrum masters)
A good responsibility matrix Helicopter view Identified all external stakeholders Identified internal roles in the project Identified major responsibilities Contract between the project and its surroundings e.g. line managers and customers
Customer interaction One persons view limited by language Not the complete Requirements
Customer interaction tools System plays Continuous participation Fixed meeting times Nagging
Risk analysis Identify risks Anticipate probability 1-5 Anticipate impact 1-5 Multiply Sort the list Follwow up
RiskProba- bility ImpactWeight OS version buggy 4520 The flu4550 Late delivery of compiler
Planning Find the soul of this particular project! What are the unique things? Where are the greatest risk? What should we prioritize? What are the real requirements?
ProductionDevelopment Repeat the same thingDo something new Over and over againand different
All Right, so how do I join you? If you wanna be one of the non-conformists, all you have to do is dress just like us and listen to the same music we do Source: South Park
The execution phase Work according to the plan... Improvise a lot
Project manager tasks Ensure it is always is clear what should be delivered Make sure there is always up to date plans Ensure that team members are motivated Ensure that clients and stakeholders "feel good" Make sure the necessary rules are followed Make sure that the momentum is sustained Ensure that decisions are made Nag, nag and nag Fix resources Report to Steering Group (Page 1 of 22)
Leadership in a project Client contact Visualize goals Fix prerequisites Ensure decisions are made Follow up Keep up the pace Motivate
Motivation Clear goal Project wanted / anchored Competence & methodology reasonable challenge Encouragment Trust Participation
Client The Project Demands The important interface Lucidity Realism
Behold the turtle, he makes progress only when his neck is out. -- DR. JAMES B. CONANT, HARVARD UNIV. PRESIDENT
... A few words about testing
Im gonna make this work Im gonna test that this works
Im gonna make this work Im gonna test that this works
Im gonna make this work Im gonna break this!
The bitter truth If you want to survive you have to deliver on time and with the right quality... Despite that the customers are always changing their mind... And subcontractors fail... And the computer says no
The way to succed Focus on client Make a proper milestone plan Define responsibilities Try to follow the plan (PMs responsibility) Improvise Work hard
Thank you!