MITM743 Advanced Project Management

1. MITM743Advanced Project Management Dr. Abdul Rahim Ahmad Assoc. Professor College of IT, UNITEN Kerzner Chapter 4 Project Management Methodologies

2. 4 Project Management Methodologies

3. PM Methodologies • Examples of methodology development • Overcoming development and Implementation barriers • Critical components • Standard Methodologies • Implementation • Tools

4. Achieving maturity in PM • 4th Phase – growth • Establish life cycle phases • Develop PM methodology • Base the methodology upon effective planning • Minimize scope changes • Select the appropriate software to support the methodology

5. 4.1 Example of Methodology development

6. Example Methodology Development • Manage business by project • Activities are treated as some sort of project • Use a standard, general, all-purpose system development methodology to guide all projects having • Well patterned methodology • Clear objectives • Well understood expectations • Thorough problem definitions

7. Good methodology • For project management and system development • Use standard tool • Reflects guidelines rather than policies • Procedures can be easily adapted on any project

8. Components of a methodology • Organizing – via project charter • In general - what to achieve and how to achieve • Forms the contract among the parties involved • Statement of business needs, what to deliver, project dependencies, role and responsibilities of members, standard for how budget and management should be approached. • Planning – • information to establish • Deliverables • Task to do • Definition of resources • Can be 4 phase: Proposal, planning, development, Implementation

9. Components of a methodology • Managing • Manage and control of process • Evaluate, assess performance, control development of deliverables, resolve issues • Reporting • Status reporting procedures; accomplishment now and to achieve, progress summary-time used, budget, schedule, impact to quality, action items. • Issues and change management procedures • Keeps project momentum • Open up discussion to solve them • Assist in keeping the project health

10. 4.2 Overcoming barriers

11. Example issues • Own methodology? • Use best practices? • Single or multiple methologies • For multiple methodologies, how can it be improved- together? Singly? • Dealing with acceptance in different department • Employees acceptance of project management • Methodologies for multinantionals

12. 4.3 Critical Components of Methodologies

13. Characteristics of Good methodology • 5 life cycle phases (maximum of 6 life cycle phases) • Overlap between phases • End of phase gate review • Integrate with other processes • Continuous improvement • Customer oriented • Company wide acceptance • Use of templates • Critical path scheduling • Simplistic, standard bar chart reporting • Minimization of paperwork • Example : ABB ICR_ABB project management1009.pdf

14. 4.4 Benefit of standard methology

15. Example standard Methodology:Microsoft Solutions Framework (MSF) • https://en.wikipedia.org/wiki/Microsoft_Solutions_Framework • https://technet.microsoft.com/en-us/library/bb497060.aspx • a set of principles, models, disciplines, concepts, and guidelines for delivering information technology solutions from Microsoft. • applicable to all IT projects like development, deployment, networking or infrastructure projects. • does not force the developer to use a specific methodology (Waterfall, Agile) but lets them decide what methodology to use.

16. MSF

17. Benefits of Standard methodology • Short term • Lower cycle time, lower cost • Realistic plan • Better communication • Provide feedback of lesson learned • Long term • Faster time to market • Lower risks • Better decision making • Customer satisfaction • Avoid internal competition in internal groups • Customer as partner • Improvements made easier

18. 4.5 Implementing the methology

19. Implementing methodology • Depends on Organizational Culture • Needs a champion – a hands on person who drive the development implementation of the methodology top down • How/where to improve • Supplier and customer interface • Explanation/description of subprocesses • Milestones • Senior management • Need of templates/metrics • Steering committee, guidebook • Educate customers on how the methodology works • Effective meetings

20. 4.6 PM Tools

21. Software tools • Software for project scheduling, to perform • Program Evaluation and review technique - PERT • Arrow diagramming method - ADM • Precedence Diagramming Method – PDM • Uses • Plan, predict use of resources within schedule and budget • Visibility and facts to make decision • Help handle uncertainties • Help check progress • Help in reporting

22. History of Tools • 1980-90 Mainframe software's • allows computerisation of planning but expensive • Difficulty to use led to low usage • 2000s – PC based tools • Open source tools – Open project, Project Libre • Free but not complete • Microsoft project • Cost a lot but comprehensive • Can import existing data • Mind Manager

23. End of Slide

24. Project Management…. Work Smart Not Hard !!!