IT elective chapter4

• Chapter 4 : Framework of project for project management
• Project Management as a Profession:

  • body of knowledge
  • standards
  • Professional organizations
  • •Currently, anyone can call him or herself a project manager
  • Unresolved issue: to what extent can an expert PM move from one industry to another?
• • Standards organizations • PMI: Project Management Institute

  • CAPM, PMP and other professional standards

  • IPMA : International Project Management Association

  • Several certifications
• Project Management Institute established in 1969
• PMI certification most popular is PMP
• Project Management Standards :

  • Standards organizations

  • PMI : Project Management Institute

  • CAPM, PMP and other professional standards

  • IPMA : International Project Management Association: http://ipma.ch/

  • Several certifications
• Project Management Professional (PMP)

  Requirements:

  • 5 years of project management experience • pass a rigorous exam • maintain ongoing professional development
• Currently over 590,000 PMPs in the world
• The CAPM or Certified Associate in Project Management only requires an exam and is considered to be a step along the way to a PMP
• PMBOK Knowledge Areas:

  • Managing Scope • Managing Time/Schedule • Managing Costs • Managing Quality • Managing Human Resources

  managing integration

  Managing Communication • Managing Risks • Managing Procurement • Managing Stakeholders
• project Scope generally defines what the project is all about
• Project Scope Forms the basis of agreement between the project SPONSOR and the project team
• Changes in the scope may be proposed at any time

  during a project, but should follow a clearly defined

  approval process
• Scope Statement:

  • Description of the scope • Acceptance criteria • Deliverables • Exclusions • Constraints • Assumptions
• A Work breakdown structure or WBS is the breakdown of the deliverables into manageable units of work.
• schedule and time management : Based on the units of work defined by the WBS
• Risk Management: Identifying potential problems and developing contingency plans to mitigate their impact.
• Software is frequently used to assist with managing the

  time schedule
• Project Cost:

  Develop a budget

  • Several methods can be used to estimate

  • Plan for the cash flow

  • Track the expenditures

  • Explain deviations and make adjustments where

  required
• project quality :

  Quality plan defines

  • The quality standards

  • The methods that will be used to achieve the standards

  • The methods that will be used to measure the standards
• human resources :

  Identification of HR requirements

  • Selection of project team

  • Development of project team

  • Motivation and management of the project team
• Communication includes within the team and with others outside the team
• The project should have a communication plan • Who needs to be communicated with • What methods will be used • What frequency • Who within the project will be responsible
• Risk represents the likelihood of the occurrence of an event that will negatively or positively impact the achievement of the project goals
• Risk Processes: • Identify risks • Analyze risks • Manage risks
• Procurement :

  Contracting to obtain supplies or services required to

  carry out the project

  • May be extremely complex

  • Time schedules can be crucial

  • On complex projects, almost always involves additional

  experts such as lawyers
• Stakeholders are people or organizations who either will be impacted by the project or who can impact the project.
• stakeholder management Always include: project sponsor, project team
• PMI Process Groups • Project Initiating • Project Planning • Project Executing • Project Monitoring and Controlling • Project Closing
• Scrum Development Overview • Known as an Agile method

  Used when requirements are difficult to define or subject to rapid change • Iterative approach • Uses sprints or 2 to 4 week cycles
• Scrum Development Overview • Roles • Product owner • Scrum Master • Development Team • May include specialist roles such as developer, subject matter expert
• Scrum Development Overview • Priorities: stories are either on the: • Front burner (currently working on) • Back burner (next up) • Fridge (for later) • Priorities are revisited before each new sprint
• Scrum Development Overview • Daily stand-up meeting (short meeting with fixed agenda) • What was done yesterday • What will be done today • Are there any problems the scrum master must address, such as resource issues out of the control of the team
• The Project Management Office (PMO) • Medium and large organizations • Typical objectives • Align projects with organizational objectives • Set standards for projects • Provide resources to project managers • Provide training and mentorship • Provide facilitation • Stay abreast of best practices in Project Management • Repository for project reports and lessons learned