1. Working on a Project Anders P. Ravn Computer Science Aalborg University April 2007

2. A Project 1.Defined Objective 2.Defined Timeframe 3.Defined Resources (Budget) Objective Project progress (uses resources) Time startfinish Harvey Maylor, Project Management, (3rd ed.), Prentice-Hall, 2002, pp 1-5

3. Project versus Line Production A project has a unique objective Variety Volume Production Project First Timers As… but … Paint by numbers Maylor pp 3-4

4. Sure Failures Ready, fire, aim It’s all in my head We do not have time for this stuff! We have a procedure for that Just common sense Failed before Won’t work here NO Objective NO defined Objective NO defined resources and process Resources are insufficient NO Defined process NO committed resources Maylor pp 7-9

5. Project versus Line Management Oversees change Fuzzy lines of authorithy Tasks change often Operates within temporary project structures Predominantly innovative Main task is conflict resolution Success defined by reaching stated end-goals Uncertainties are in intrinsic in the process Maylor pp 10

6. The Process Maylor pp 15-18 Time Objective Result Constraints Resources

7. Life-cycle 1.Define the project objective 2.Design the process 3.Deliver the product 4.Develop the process Product Constraints Resources Maylor pp 19-24 Objective

8. Defining an Objective Conceptualisation Product Requirement Definition Feasibility Analysis Complexity Resource Budget: - people (skills, time, availability) - tools and materials (cost, availability)

9. Define Objective A concise description of the result expressed in natural language Ckeck completeness by FACTOR: Functionality for end use Application Domain of end use Conditions for success Technology to be used Objective key components and concepts Realization conditions Lars Mathiassen, Andreas Munk-Madsen, Peter Axel Nielsen and Jan Stage, Object-oriented Analysis and Design, MARKO Publishing, Aalborg 2000.

10. Estimating Complexity Technical Resource Organizational HighLow Factor Maylor pp 28-31

11. Feasibility - Issues to address Strategy Structure Systems Staff Skills Style/Culture Stakeholders Maylor pp 24-27

12. Designing a process Proposal – Product Specification Plan (activities, milestones, dependencies) Justification (costs and benefits - SWAT) Agreement

13. Planning – why bother? Customer expectations Project progress The solution space To be able to act rationally when – forseeable - events happen. Livet forstås baglæns, men må leves forlæns Søren Kierkegaard

14. Planning – how? Time Activity Deadline Milestone

15. Gantt Chart – a useful tool Activity A B C …

16. Pert Diagram -dependencies A 14 B 7 C 10 D 13 F 7 E 14 G 5 H 6 I 24

17. Example Gantt Chart

18. Delivering the product Start-up Execution (check MILESTONES) Completion Handover (or flee!)

19. Example: Status

20. Develop your Process Review the material and the result Feedback There is no success like failure, ’though failure is no success at all Bob Dylan

21. The Material Journal – Agendas, Minutes, Notes Product Components – Work Items Schedule – Milestones, Activities

22. Your Journal (project binder) Notes (chronologically ordered) Project idea – the problem to be investigated (Work Packages – subprojects in a larger project) Issues – and ways to resolve them Meetings and minutes Schedules – and rationale for changes Work Item Descriptions

23. The Project Structuring Elements Meetings Group Organization

24. Meetings - preparation Decide on the purpose(s) What is the agenda? - main and side points For each point: - discussion - briefing - decision Prepare agenda – assign duration to each point

25. Standard Agenda 1.Comments to the agenda … N-1. Next meeting N. Other matters

26. The Meeting Keep the time Take notes for minutes Record issues – do not resolve them

27. Organization - Players Customer – has the problem and has to be satisfied with the solution Project Team – works to find a solution Boss – defines the resources and monitors progress Consultant – contributes ideas and expertise

28. Team - roles Designer – develops solutions Developer – develops components Integrator (tester) – ensures consistent releases Documenter – ensures documentation Organizer (planner) – keeps orderly progress

29. If you remember nothing else: Define your objective Have a plan Know your resources – team roles Have an agenda for meetings