1 / 44

Project Planning and organisation

Project Planning and organisation. 1.0. u lf.bergqvist@nordforce.se www.nordforce.se. 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.

piper
Download Presentation

Project Planning and organisation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project Planning and organisation

  2. 1.0

  3. ulf.bergqvist@nordforce.se www.nordforce.se

  4. What is a Project? Reach a defined goal With limited resources Within a fixed time

  5. Planning • To think about: • What are we supposed to achieve? • How do we get there?

  6. 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

  7. 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

  8. What is the right planning? ?

  9. Some useful tools • Mile stone plan • Responsibility matrix • Customer interaction tools • Risk analysis

  10. Milestone plan

  11. When the system architecture description is approved by Product owner and System architect 10 2013-12-12

  12. A good milestone plan • ”Helicopter view” • State oriented, what not how • 10-15 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

  13. Responsibility matrix

  14. Legend R= Responsible (incl. execution) E=Executes D=Makes decision I=Should be informed A=Advisor

  15. Responsibility matrix

  16. Roles that tend to lead to success • Project manager • System architect • Client ”nagger” • Integration responsible • Test responsible • CM responsible • Team leads (scrum masters)

  17. 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

  18. Customer interaction One person’s view limited by language Not the complete Requirements

  19. Customer interaction tools • System plays • Continuous participation • Fixed meeting times • Nagging

  20. Risk analysis • Identify risks • Anticipate probability 1-5 • Anticipate impact 1-5 • Multiply • Sort the list • Follwow up

  21. PlanningFind 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?

  22. ProductionDevelopment Repeat the same thing Do something new Over and over again and different

  23. 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

  24. The execution phase Work according to the plan ... Improvise a lot

  25. Project manager tasks (Page 1 of 22) Ensure it is always is clear what should be deliveredMake sure there is always up to date plansEnsure that team members are motivatedEnsure that clients and stakeholders "feel good"Make sure the necessary rules are followedMake sure that the momentum is sustainedEnsure that decisions are madeNag, nag and nagFix resourcesReport to Steering Group

  26. Leadership in a project • Client contact • Visualize goals • Fix prerequisites • Ensure decisions are made • Follow up • Keep up the pace • Motivate

  27. EncouragmentTrustParticipation reasonable challenge Competence & methodology Clear goal Project wanted / anchored Motivation

  28. The important interface Client Demands Demands LucidityRealism The Project

  29. Behold the turtle, he makes progress only when his neck is out. -- DR. JAMES B. CONANT, HARVARD UNIV. PRESIDENT

  30. ... A few words about testing

  31. I’m gonna make this work I’m gonna test that this works

  32. I’m gonna test that this works I’m gonna make this work

  33. I’m gonna break this! I’m gonna make this work

  34. 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”

  35. The way to succed • Focus on client • Make a proper milestone plan • Define responsibilities • Try to follow the plan (PMs responsibility) • Improvise • Work hard

  36. Thank you!

More Related