Use of PSP task in a SW component
Brought to you by:
ken_raisor,
tuma
Menu
▾
▴
Hi all:
For a team project in Dashboard, when you create the tasks under a Software Component on the WBS, you could either use a "PSP Task" or you can add the specific tasks (e.g., Plan, DLD, ... UT). Why would you choose one over the other? If I use the "PSP Task", am I able to access more reports?
rfrederi
Using a PSP Task means that you have all of the PSP functionality available: you can use the Size Estimating Template and PROBE to refine your estimate for the task; your personal historical data is used to generate estimates for time in phase and defects; and you see the traditional PSP scripts and plan summary forms. In addition, when you finish the PSP task, it will be added to your personal historical dataset, and will appear in the charts and reports in the Data Analysis center.
All of those things are possible because the PSP is a defined, repeatable process. Some teams don't like defined processes, however, and they prefer to create individual phase elements. For example, some agile teams use a test-driven development style where Code / Compile / Test all blend into a single activity. These teams don't like the structure imposed by the PSP, and they prefer to create individual phase elements.
But when you give up the repeatable process structure of the PSP Task, you're now creating a collection of tasks that could be potentially arbitrary. Without the guarantee of repeatable structure, the dashboard can no longer apply the high-maturity PSP concepts to the work. So individually created phase tasks will not be able to use PROBE, PSP scripts/forms, etc.
One other scenario I've seen is this: some teams like the defined structure of PSP, but they are dividing the work between two people in unusual ways: for example, having Person A do the Planning and Design, then passing the work over to Person B for Code and Test. This task delegation style breaks the historical data assumptions made by the PSP. (PSP is the *Personal* software process, after all.) In such cases, teams are better off creating separate tasks for each phase instead of creating "PSP Task" objects.
Ultimately, it comes down to the planning style and high-maturity preferences of the team in question. The dashboard will support either approach.
David:
As always, thanks for you prompt, thoughtful and insightful reply.
I left out a few details:
--This is for a MS-level Software Engineering course with two TSPi cycles;
--Only about 50% of the class has PSP background;
--None of those who do have PSP experience used the Personal Dashboard for their PSP work.
We will use the full PSP set of phases for the implementation work (Plan, DLD, DLDR, Code CodeReview, Compile, UT, PM) and add DLD Inspection, Code Inspection, Component Quality Review, ... as in TSPi. These don't show up on the Personal Dashboard Project Summary form, but they do show on the TSPi forms I created (similiar to SUMP and SUMQ) in the Team Dashboard. The negative part of using PSP is that the Software Component tasks are out of time sequence when you use PSP.
I think in my case, I will not use the "PSP Task", but rather enter the specific tasks. I will lose the PSP forms, but I think I can live with that. I think I will have a better education environment.
rfrederi
I'd like to add one extra comment for the benefit of people who view this thread in the future. When you use a "PSP Task", the inspection phases will be out of time sequence immediately following a "Sync to WBS" operation. So after the sync, individuals should open their Task & Schedule window and use the "Flat View" to place the inspections in the desired sequence, then save the changes. From that point on, these tasks will fall in correct chronological order.
Of course, "Flat View" is not strictly for reordering inspection phases. It is rare for tasks to be performed in the exact order that they appear in the hierarchy, so individuals should generally be updating the "Flat View" task ordering whether they use PSP Tasks or not. (In practice, some individuals do not remember and/or bother to complete this step.)