1 / x project planning cmmi project planning jean-luc deprez robin leblon

1 / xProject Planning

CMMIProject Planning

Jean-Luc DeprezRobin Leblon


Project PlanningPurpose

Make an assessment of all time and resource consuming activities needed to complete the project

Allow management/predictions based on assessment


Project PlanningSpecific Goals

SG 1 Establish Estimates SP1.1 Estimate the Scope of the Project

Non-formal WBS derived from Product Decomposition Mapped to Trac ticket and roadmap system for activity and

milestone planning SP1.2 Establish Estimates of Work Product and Task

Attributes Only Multitouch estimates time needed in hours, no specific model

used Time estimation other teams, mapped to weeks?

Technical Decisions: architecture docs previous semester, experience and extra research

[1],[2],[3],[4] Trac server

[4] Trac server Multitouch



SG 1 Establish Estimates SP1.3 Define Project Lifecycle

Multitouch milestone moving == review meeting Hadra, Sprint evaluation and planning == review meeting

artifacts (backlogs)? Mashed Up & WAFL about weekly milestone

WAFL planning? Iterative development: Expanding functionality

[1],[2],[3],[4] Trac server

[ 6] Mashed Up Planning



SG 1 Establish Estimates SP1.4 Determine Estimates of Effort and Cost

Most project work unprecedented Sensible estimates based on personal jugement

All projects have identified risks and critical required competencies

Work time collected by all project may be of use for future projects[7],[8],[9] Time caputuring



SG 2 Develop a Project Plan SP2.1 Establish the Budget and Schedule

All projects have defined milestones Dependencies on by milestone basis Technology and risk research done early-on to protect dependent

activities (company policy) Most important resource is manpower

assigned on a by milestone basis

[1],[2],[3],[4] Trac server



SG 2 Develop a Project Plan SP2.2 Identify Project Risks

Risk management is company policy early mitigation strategies

Risk lists Mashed Up and WAFL? Risk list Hadra: many risks still open?

SP2.3 Plan for Data Management No data management policies have been formalized Some conventions for modifing the colaborative environments

appear to be in place per project

Lack of wiki structure policy Some projects wiki’s risk navigation difficulty

[10],[11] Risk lists

[12],[13] Collaborative environment Guidelines



SG 2 Develop a Project Plan SP2.4 Plan for Project Resources

Implicit man-hours allocaton through Trac Ticket ownership (Ticket maps to task) Membership of a dedicated team (e.g. devteam)

All teams have server for CE Multitouch reserved time on Multitouch table

(no succes so far, UGent == bad suplier) SP2.5 Plan for Needed Knowledge and Skills

No artifacts point out a available skill inventory(exception: Hadra Ruby experts)

All Teams have multiple references to aquiring needed skill’sTickets, Wiki, Reports…

[1],[2],[3],[4] Trac server

[1],[2],[3],[4] Trac server



SG 2 Develop a Project Plan SP2.6 Plan Stakeholder Involvement

WAFL has stakeholder involvement plan (artifact?) General stakeholder involvement:

Coaching session Customer/Management meeting Review meeting Customer/Senior managemet meeting

SP2.7 Establish the Project Plan Roadmap serves as overall project plan Crude planning in place within 2 weeks

[1],[2],[3],[4] Trac server

10 / x<Process Area>

Process PlanningGeneric Practices GG 2

GP2.1 Establish an Organizational Policy All projects have taken considerable time to make a feasible

project planning.

GP2.2 Plan the Process Most groups have not “planned the planning” Hadra had a well defined planning procedure (SCRUM)

GP2.3 Provide Resources Most groups have not used any extra resources for planning.


Process PlanningGeneric Practices GG 2 (2)

GP2.4 Assign Responsibility All teams have assigned a project manager No specific responsibilities have been assigned for planning

GP2.5 Train People No specific training in respect to planning

GP2.6 Manage Configurations All projects use trac ticketing and wiki. Some teams also include planning information in the version

control system

[1],[2],[3],[4] Trac server



GP2.7 Identify and Involve Relevant Stakeholders Required review meetings for customer involvement Hadra has defined team involvement through SCRUM

GP2.8 Monitor and Control the Process Hadra, corrective actions besides the SCRUM’s? Multitouch : follow-up of tickets after each milestone, transfer

if needed. Wafl : overdue tickets treated as risks and mediated as fast

as possible

[14] Hadra SCRUM



GP2.9 Objectively Evaluate Adherence Other than evaluation at review meetings no project has

compared its planning to the planning standards and procedures

GP2.10 Review Status with Higher Level Management Review meetings with customer Some groups have altered their planning after review with

customer


Process PlanningGeneric Practices GG 3

GP3.1 Establish a Defined Process Besides Hadra, no project had a planning process according

a certain procedure or standard

GP3.2 Collect Improvement Information Idea : implement a knowledge base, so planning experience

can be shared and preserved


Project PlanningProcess Assets

[1],[2],[3],[4] Trac server allows managing activities and milestones

Wiki allows knowledge management

Integrated with SVN version control



Wiki



Roadmap



Tickets


Project PlanningFindings

Strengths Responsibility through Trac ticket onwership helps work

progress

Opportunities for Improvement More detailed planning of activities and there dependencies

possible (e.g. Gantt-Chart)

Proposed Actions Look to extend Trac to aid this, or find other Ticket system Reuse man-hour data produced this year


Project PlanningReferences

[1] Trac server Hadra http://hadra.stoneship.org/trac/hadra

[2] Trac server Mashedup https://157.193.215.149/trac/

[3] Trac server WAFL http://bellerophon159.test.atlantis.ugent.be/trac/wiki

[4] Trac server Multitouch http://bellerophon162.test.atlantis.ugent.be/trac/main/wiki

[5] CMMI for Development version 1.2http://www.sei.cmu.edu/publications/documents/06.reports/06tr008.html

[6] Mashed Up planninghttps://157.193.215.149/trac/wiki/Planning



[7] Time tracking Multitouchhttp://bellerophon162.test.atlantis.ugent.be/trac/main/report/11?BILLABLE=1&UNBILLABLE=1&REOPENED=reopened&ASSIGNED=assigned&CLOSED=closed&NEW=new&ACCEPTED=accepted&STARTDATE=0&ENDDATE=2000000000

[8] Time sheets Masheduphttps://157.193.215.149/trac/browser/trunk/documentation/team/timesheets

[9] Time sheets WAFLhttp://bellerophon159.test.atlantis.ugent.be/wiki/index.php/Timesheets

[10] Risk Multitouch http://bellerophon162.test.atlantis.ugent.be/trac/main/report/24

[11] Warroomlist Hadrahttp://hadra.stoneship.org/trac/hadra/wiki/Warroomlist


Project PlanningGlossary

CMMI Capability Maturity Model Integration

CE Colaborative Environment

WBS Work Breakdown system



[12] Commit Guidelines Hadra http://hadra.stoneship.org/trac/hadra/wiki/CommitGuidelines

[13] Richtlijnen Multitouch http://bellerophon162.test.atlantis.ugent.be/trac/main/wiki

[14] Hadra SCRUMhttp://hadra.stoneship.org/trac/hadra/wiki/SCRUM

1 / x project planning cmmi project planning jean-luc deprez robin leblon

Documents