» Planning
Project Management Process: Setup
THE PLANNING PHASE EXPLAINED
The Planning process is divided into numerous important steps, explained in detail below:
STEP 1: ORGANIZATION
The project organization defines the roles and how they work together within the core teams, the development teams and the entire project organization.
Main goals of the project organization are to ...
... find an appropriate project organization that fits best to planned project scope
... provide an orientation for project stakeholders and the project environment
... provide a communication element
... have a base for the definition of responsibilities
The organization is visualized via a standardized template – see an template image
For SW development projects the following major project roles are defined:
- Project Manager (PM)
- Team Lead (TL)
- Software Architect (SWA)
- Software Engineer (SWE)
- Quality Assurance Engineer (QAE)
STEP 2: COMMUNICATION
The project communication defines how the necessary information flows through the project organization.
Within complex organization there are three meeting platforms installed in order to assure a proper communication flow:
- Project Steering Board (PSB)
- Project Controlling Meeting (PCM)
- Project Team Meeting (PTM)
The communication structure is visualized via a standardized template.
STEP 3: RISK ANALAYSIS
Risk Analysis will be done separately for each project within the program. The initial RA takes place in the appropriate Kick Off Meeting with the whole project team and stakeholders Risk Analysis is a 4 step process:
Step 1: List all standard risks according to the technical process and identify additional risks using the brainstorming method
Step 2: Cluster listed risks to categories
Step 3: Estimate potential damage and probability of occurrence for each risk Use a scale from 1 (low) to 3 (high) for each case
Step 4: Define preventive respectively corrective measures for high risks
STEP 4: EFFORT ESTIMATION
This step will be explained later in more detail.
STEP 5: SCHEDULING
Step 1: Track all tasks to MS Project File (standard template) to Backlog
Step 2: Assign resources to each task
Step 3: Add effort according to estimation file
Step 4: Define technical dependencies
Step 5: Define resource dependencies
Step 6: Do detail planning for Sprint 1
Legal & Privacy Policy
office@alturos.com
www.alturos.com