Wednesday, September 16, 2015

PMBOK Framework vs Agile Methodology

PMBOK Framework vs Agile Methodology

PMBOK Framework
Agile Methods

XP eXtreme programming
FDD Feature Development
Project Integration Management
·         Develop Project Charter
·         Develop Preliminary Project Scope Statement
·         Develop Project Management Plan
·         Direct and Manage Project Execution
·         Monitor and Control Project Work
·         Integrated Change Control
·         Close Project

·         Integration of software as soon as possible and as often as possible (mostly related with software code)
·          Collective code ownership
·         Project velocity measurement
·         Verification of management approval and funding during planning phase
·         Validation of development tools and infrastructure during planning phase
·         Strong change management  procedure with product and sprint backlog
·         Refinement of system architecture to support changes
·         Postgame phase
·         Development of the overall system model
Project Scope Management
·         Scope Planning
·         Scope Definition
·         Create Work Breakdown Structure (WBS)
·         Scope Verification
·         Scope Control
·         User Stories
·         Release Planning, Small Releases 

·         Perform domain analysis for  building domain model
·         Development of a comprehensive product backlog list
·         Development of a comprehensive  product sprint backlog
·         Definition of the functionality that will be included in each release.
·         Selection of the release most appropriate for immediate development.
·         Review of progress for assigned  backlog items
·         Perform domain analysis for building domain model (step1).
·         Build Features List, subject areas  (step 2)

Project Time Management

·         Activity Definition
·         Activity Sequencing
·         Activity Resource Estimating
·         Activity Duration Estimating
·         Schedule Development, and
·         Schedule Control
·         Release Planning
·         Iterations planning
·         Definition of the delivery date and functionality for each release
·         Monthly iterations
·         Determine development sequence (step 3)
·         Assign Business Activities to Chief Programmers (step 3)
·         Assign Classes to Developers(step 3)
·         Chief programmer work package.

Project Cost Management
·         Cost Estimating
·         Cost Budgeting, and
·         Cost Control project
·         Not Available
·         Estimation of release cost, during planning phase
·         Not Available
Project Quality Management
·         Quality Planning,
·         Perform Quality Assurance, and
·         Perform Quality Control
·         Emphasize on testing(unit, acceptance)
·         Based on simplicity
·         Use of project standards

·         Distribution, review and adjustment of the standards with which the product will conform
·         Design review meeting
·         Sprint planning meeting
·         Sprint review meeting
·         Daily scrum

·         Review meetings (all steps)
·         Code inspection and unit test(step 5)

Project Human Resource Management
·         Human Resource Planning
·         Acquire Project Team
·         Develop Project Team, and
·         Manage Project Team
·         Personnel rotation to various positions
·         Pair programming
·         Good working conditions(no overtime)

·         Appointment of project team(s)  per release
·         Team participation in sprint meetings
·         Team participation in daily scrums
·         Appoint modeling team (step1)
·         Appoint feature list team(step 2)
·         Appoint Planning Team(step 3)
·         Appoint Feature Team (step3)
Project Communications Management
·         Communications Planning
·         Information Distribution
·         Performance Reporting, and
·         Manage Stakeholders
·         Use of system metaphor
·         Customer always available
·         Daily meetings
·         Use of project standards

·         Design review meeting
·         Scrum meeting
·         Sprint planning meeting
·         Sprint review meeting
·         Communication of standards to the project team

·         Review meetings (all steps)
Project Risk Management
·         Risk Management Planning
·         Risk Identification
·         Qualitative Risk Analysis
·         Qualitative Risk Analysis
·         Risk Response Planning, and
·         Risk Monitoring and Control
·         Create prototype to limit risk

·         Initial assessment of risk during pregame
·         Risk review during review meetings

·         Not available

Project Procurement Management
·         Plan Purchases and Acquisitions
·         Plan Contracting
·         Request Seller Responses
·         Select Sellers
·         Contract Administration
·         Contract Closure

·         Not available

·         Not available

·         Not available

Table above proves that agile methods do not define all facets needed in order to cover all aspects of project management, in the traditional sense. This was partially expected since traditional project management processes are fully defined compared with agile methods that are considered “practical”

Following Agile methods are giving emphasis in the following knowledge areas:
·         Scope Management, since emphasis is given in managing requirements
·         Human resource management, since emphasis is given in team work
·         Quality management, even though not formally defined, use of standards, testing and frequent reviews are promoted.
On the other hand, agile methods do not fully address the following knowledge areas:
·         Risk is not managed explicitly
·         Cost management is not part of the agile methodologies
·         Procurement management is not addressed at all
This implies that connecting agile methods with PMBOK will benefit the software project management community

No comments:

Post a Comment