Presentation is loading. Please wait.

Presentation is loading. Please wait.

The Personal Software Process Alan Kelon Oliveira de Moraes May 15, 2006 - Recife.

Similar presentations


Presentation on theme: "The Personal Software Process Alan Kelon Oliveira de Moraes May 15, 2006 - Recife."— Presentation transcript:

1 The Personal Software Process Alan Kelon Oliveira de Moraes alan@kelon.org May 15, 2006 - Recife

2 To do an effective job, you need to... ● Plan your work ● Do your work according to this plan ● Strive to produce the highest quality products

3 Personal Software Process (PSP) ● It is a disciplined way of writing software which can lead to dramatic improvements in – the quality of the software you write – your productivity – the quality of your plans and estimates. ● Following a discipline like this can lead to greater self-knowledge, a valuable thing in itself

4 Personal Software Process (PSP) ● It shows how to apply advanced engineering methods to their daily tasks ● Provides detailed estimating and planning methods ● Shows how to track sw engineers' performance against these plans ● Explains how defined process can guide their work ● Will lead you away from random hacking and towards professional software engineering

5 Keywords ● Responsible ● Repeatable ● Informed ● Rational ● Aware ● Mature

6 PSP is not... ● a Silver Bullet solution ● a radically different approach to development

7 PSP is ● a framework that allows detailed planning and tracking of project status ● a vehicle to collect “in process” metrics to provide insight and opportunities to improvement ● a way to protect development steps needed to “build in” quality

8 Benefits ● PSP has the potential to increase your effectiveness as a programmer dramatically ● The data you collect and the conclusions you infer from them can empower you in negotiations with your boss ● Deeper benefits are possible too. Any self- knowledge has the potential to lead to personal growth

9 Best practices ● Task breakdown (detailed planning) ● Time alloted to Design ● Size estimation methods ● Time alloted to Review/Inspection ● Time tracking ● Defect tracking ● Metric analysis ● Coding standards

10 What does PSP provide? ● Measurements – Size – Time – Defects

11 Time estimating error

12 Defect Level Improvement

13 Productivity Results

14 PSP processes

15 PSP Process Flow

16 Time management ● You will likely spend your time this week much the way you spent time last week ● To make realistic plans, you have to track way you spend time ● To check the accuracy of your time estimates and plans, you must document them and latter compare them with what you actually do

17 Time management ● To make more accurate plans, determine where your previous plans where in error and what you could have done better ● To manage your time, plan your time and them follow the plan

18 Tracking time ● Categorize your major activities ● Record the time spent on each major activity ● Record time in a standard way ● Keep the time data in a convenient place ● Hint: – When you occasionally forget to record the start time, stop time, or interrupt duration, make an estimate as soon as you remember

19

20

21 Period planning ● A period plan concerns the way you plan to spend time during the period (day, week, month) ● The weekly Activity Summary

22

23

24 Product planning ● The product planning is based on an activity, like developing a program or writing a report ● The Job Number Log

25 Program size

26 Managing your time ● Decide how you want to spend your time ● Make a time budget ● Track the way you spend time against this budget ● Decide what changes to make to bring your actions into agreement with the budget ● Prioritize your time

27 Managing commitments ● A true commitment requires an explicit agreement between two or more parties on: – what will be done – the criteria for determining that it is done – who will do it – when it will be done – the compensation or other consideration to be given in return – and who will provide this compensation or consideration

28 Managing commitments ● Analyze the job before agreeing to the commitment ● Support the commitment with a plan ● Document the agreement ● If unable to meet the commitment, promptly tell the other part and try to minimize the impact on the that person

29 Managing commitments ● The consequences of not managing commitments – work required exceeds time available – Failure to meet commitments – Misplaced priorities – Poor quality of work – Loss of trust – Loss of respect for your judgment

30 Managing schedules ● Make a project schedule ● Checkpoints ● Track project plan

31

32


Download ppt "The Personal Software Process Alan Kelon Oliveira de Moraes May 15, 2006 - Recife."

Similar presentations


Ads by Google