Project planning. Planning process. What is a project? The project plan

Size: px

Start display at page:

Download "Project planning. Planning process. What is a project? The project plan"

Brandon Gibson
5 years ago
Views:

1 Planning process Project planning Kristian Sandahl Planning is the processes for the processes Planning is also a development perspective Planning is about refining processes: the worldly level assigns activities to the process model, defines tasks and measures the atomic level is detailed description of input and output What is a project? A temporal organisation with specific goals: Functions Quality Time Resources The project plan Shall always be written down. Shall be readable to all stakeholders of the project. We ll go through some important parts of a project plan with theory and recommendations. 1

2 Administrative information Project identity Members: name, role, phone, Version number Mailing lists Home pages Customer contact Table of contents Overview Purpose Prioritised goal(s), sub goals, internal goals Limitations and constraints: Hardware Resources Time Technology Knowledge Stake-holders: primary, secondary, indirect Phase plan Same management, different development prestudy feasability study inception elaboration transition conculsion Topic for the project plan prestudy feasability study analysis design testing conculsion System development phases construction execution Project managment phases System development phases implementation execution Project managment phases 2

3 Organisation Place of the project Teams Roles Responsibilities Authorities Communications Documents Recommended roles: Project leader Lead analyst Architect Test leader Librarian/Knowledge manager Testers should be independent Project manager Has the final word on all matters Manages resources Ensures goals Makes staffing Plans Reports internally, externally Leadership Social skills High technical skill Lead analyst Defines services provided Captures requirements Models the forthcoming system Handles contacts with customer and users Has the final word on requirements interpretations Assists marketing Writes requirements specification Very good communication skills High analytical skills Good domain and business knowledge Architect Has the final word in technical matters Decide and specifies: target environment high-level architecture sourced components external interfaces Ensures requirements Highest possible technical skills Leadership Social skills 3

4 Test leader Evaluates requirements Creates and selects test cases Creates and maintains a test environment Feed-back test results Decides the status of the product Very high analytical skills Very high technical skills Skills in statistics Sometimes the default deputy PL Librarian/Knowledge manager Keeps documents in good order Makes documents available Follow-up on administrative decisions Collects time-reports Identifies reusable components Creates common experience Very high sense for good order Experience as developer Other useful roles Documentation plan Development manager Procurement manager Economic controller Quality coordinator Deployment responsible Technical writer Course developer Internal: Minutes of meetings Meeting agendas Time reports Experience build-up Inspection records Accounting Group contract Mile-stone review External: Requirements specification Design specification Test report Manuals Economic communication Promotion material Toll-gate preparation 4

5 Training and education Resource plan Internal: Tools Techniques Methods Maturity External: Customers Users Operation People: Expertise Availability Premises Hardware Software Testing equipment Travelling Customer time Budget Meeting plan Type of meeting Frequency Process Participation Communication genres Negotiations: Constructive Side-effects Workshops: Reduced lead-time First-hand information is spread 5

6 Mile-stone and tollgate plan Toll-gate Mile-stone Plan and follow-up outcome follow-up periods Decision about the continuation of the project by external committee Verifying sub-goal fulfilment. Can be done internally. initial plan time Activities Gantt chart Number Name Resources Duration no Break 1 down per 2 person 3 descr interv UML spec who A,K K,U K w1 5 w2 2 w3 5 w4 25 time(h) I T as 'D3 u '3 '3 ' 3 ' 3 ' 3 ' 3 ' 3 ' 3 ' 3 ' 3 ' 3 ' 3 ' För d 2 Inleda 5 3 Insa m 1 4 Syste 1 5 Kravs 2 6 Proj 2 7 B 2 8 Redov. 1 9 Inlä m n. 1 Huv 28 d d 1 D 5 1 B 5 1 S yste m m 1 1 Inläm ni 1 K o 1 1 S yste m m 1 1 T e stf 5 1 T e 5 1 B 2 2 Inläm ni 2 Inte 5 2 S yste m 1 2 B 3 4 val M,K S yste m m öte R e d 1 2 Projek 1 d t t ä 2 Sam m anst 7 2 B 3 2 Inläm ning 3 Insam lin 3 H a lvti 1 3 U tv 1 3 K i 1 3 K i 1 6

7 Quality and Change Risk analysis Quality plan: Tests: unit test system test integration test acceptance test Inspections Reviews Measurements Follow-up Experience feed-forward Change plan: Request Process Decision Documentation Configuration management Follow-up risk PL ill delay risk PL ill delay probability severity risk remedy cost risk 6 4 threat Introduction of project plan Project overview Main deliverables Main milestones Library for documents and code Definitions Communication with stake-holders Project management process Staffing Priorities Philosophy Risk management Task refinement Routines for reporting 7

8 COCOMO Effort = C1 EAF (Size) P1 Effort = number of staff months C1 = scaling constant EAF = Effort Adjustment Factor Size = number of delivered, human produced source code instructions (KDSI) P1 = exponent describing the scaling inherent of the process COCOMO Time = C2 (Effort) P2 Time = total number of months C2 = scaling constant P2 = Inherent inertia and parallelism in management DELPHI Present information for expert panel Meet to discuss a common view Independent, personal estimates Summary Discussion and second round 8

Project Management. Agenda - What will you learn today? Theory Lecture Plan. A Software Life-cycle Model Which part will we talk about today?

Project Management. Agenda - What will you learn today? Theory Lecture Plan. A Software Life-cycle Model Which part will we talk about today? Theory Lecture Plan 2 Lecture 2 Software Engineering TDDC88/TDDC93 Autumn 2008 Slides by Presented by Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden krisa@ida.liu.se