Project Management Methodology

1. Project Management Methodology Planning for Human Resources

2. People Management - Team • Build the right team • Be prepared to changes • Assign roles and responsibilities • Monitor the team performance • Support high spirit of the development team

3. Project Organizational Chart • The chart shows a project assembled team structure • Normally created first in roles, and then, has people assigned to the roles • Mandatory roles: • Product manager • Technical leader • These 2 roles must not be assigned to the same person

4. Organizational Chart Sample

5. RACI matrix • Each team member must be assigned to specific task(s) shown in WBS • In addition to that, for management and communication activities, RACI matrix is recommended • Each team member should be assigned with one or more RACI features

6. RACI matrix • RACI stand for • R- responsibility, in other words, a doer • A – accountability, one who is ultimately accountable • C – Consultation, one who provides vision and advises • I – Informed, one who is to be informed about the project performance

7. Resource loading • Watch for correct resource loading when you assign people to the WBS tasks • Apply resource levelling technique when someone is overloaded • The technique suggests review of slack allowances in order to create a smoother distribution of resource usage • Levelled resources require less management, lower costs, produce fewer personnel and accounting problems, improve morale

8. Build the right team • Acquire required skills • Have everyone understanding of the role and responsibilities • Setup organizational model • Motivate the team on the go • Provide required training • Project manager must be a leader by nature

9. Team models • Business team • Peer group headed by technical leader • Team members are differentiated by the area of expertise • All the members are equal • Technical leader is supposed to make technical decision • Most often in use for regular IT projects

10. Team models • Chief-Performer Team • Chief-performer is one with very high productivity and skills, much higher than the others’ • He/she is supposed to do major part of work, including design and implementation • The others are involved for help only • Used for special kind of projects, where a special skill is required

11. Team models • Feature team • Team members represent different areas of the project development • They all are responsible for the decisions made • Often is created to resolve the issues, for example of bad performance

12. Security Projects Teams • Access to sensitive data and technology dictates the need of • Thorough background check • Reliable references • Particular level of security clearance

13. Planning for cost • Work cost - the cost of work force engaged into the project. Calculated on the basis of rates • Fixed cost – cost that does not depend on a task duration • Material cost – the cost of consumable materials

14. Resource levelling • Assign resources to the tasks • Generate the resource usage report • Request for resource levelling • Resource levelling will eliminate overloading by splitting the tasks