The Project Management Body of Knowledge (PMBOK) is an intentionally recognized standard (IEEE, ANSI) that deals with the application of knowledge, skills, tools and techniques to meet project requirements[1]. PMBOK is structured around five process groups (initiating, planning, execution, controlling and closure) and nine knowledge areas (integration management, scope management, time management, cost management, quality management, human resource management, communication management, risk management and procurement management)[1].
On the other hand, agile methods are based on the principles of embracing change, focusing on customer value, delivering part of functionality incrementally, collaborate, reflect and learn continuously. However, few studies conducted illustrate that agile project management methodologies cannot be considered complete, from the traditional project management point of view, since a number of processes either are missing or not described explicitly[1]. So in order to meet the proper project requirements agile methods should adapt, use and implement Project Management Body of Knowledge (PMBOK) guidelines.
Open Unified Process (OpenUP) surely had steps in which it can help its developers create a system efficiently with the guidelines of PMBOK. Open Unified Process or OpenUP is an iterative software development process that is minimal (only fundamental content is included), complete (can be manifested as an entire process to build a system) and extensible (can be used as a foundation on which process content can be added or tailored as needed)[3] . OpenUP is an agile process. Though OpenUP is lightweight, there is much more to agility than simply being light. OpenUP has the essential characteristics of a lean that applies iterative and incremental approaches within a proven structured lifecycle. OpenUP is based on use cases and scenarios, risk management, and an architecture-centric approach to drive development[4]. OpenUP process, though complete in its target coverage and context, also serves as a base process upon which additional process content can be built. Plug-ins can extend OpenUP to include guidance for large-scale techniques (such as Model-Driven Development) and lighter, agile techniques (such as Agile Database Techniques). Tool vendors can create plug-ins that attach tool mentors to tasks giving step-by-step instructions on how the tool can be used within the context of the process. In addition to this community of plug-ins that can be mixed and matched to build a tailored process – and possibly more important for the goal of having a process that meets the specific needs of a particular project – the Eclipse Process Framework Composer tool can be used to author in-house content. Organization-specific templates can be integrated into the process content and new process elements from checklists and guidance to brand new roles, tasks, and work products can be introduced [4].
OpenUP Phases include:
Inception Phase Iteration[4]
In this phase, developers analyze the things that should be built, identify the system functionality, cost, schedule, risks.
Elaboration Phase Iteration[4]
This phase deals with the design, implementation, validation of an architecture, understanding of the requirements, and alleviation of possible risks that might occur.
Construction Phase Iteration[4]
Develop a complete product for its user community and minimize development cost to achieve some degree of parallelism
Transition Phase Iteration[4]
After the product is deployed, beta testing is needed to validate if user expectations are met and achieve stakeholder agreement that deployment is complete.
As a summary, OpenUP is a minimal, complete and extensible process. It fosters agile techniques and principles, while has a proven structured lifecycle that emphasizes the continuous delivery of quality software that is valuable to stakeholders.
References:
1. Jean-Michel de Jaeger. PMI - PMBOK guide (Third Edition 2004). Retrieved 29Nov09.
2. P. Fitsilis. Comparing PMBOK and Agile Project Management Software Development Processes. Retrieved from
3."Eclipse Process Framework Project". Eclipse. Retrieved from
4.Ricardo Balduino. Introduction to OpenUP. August 2007. Retrieved 29Nov09.
On the other hand, agile methods are based on the principles of embracing change, focusing on customer value, delivering part of functionality incrementally, collaborate, reflect and learn continuously. However, few studies conducted illustrate that agile project management methodologies cannot be considered complete, from the traditional project management point of view, since a number of processes either are missing or not described explicitly[1]. So in order to meet the proper project requirements agile methods should adapt, use and implement Project Management Body of Knowledge (PMBOK) guidelines.
Open Unified Process (OpenUP) surely had steps in which it can help its developers create a system efficiently with the guidelines of PMBOK. Open Unified Process or OpenUP is an iterative software development process that is minimal (only fundamental content is included), complete (can be manifested as an entire process to build a system) and extensible (can be used as a foundation on which process content can be added or tailored as needed)[3] . OpenUP is an agile process. Though OpenUP is lightweight, there is much more to agility than simply being light. OpenUP has the essential characteristics of a lean that applies iterative and incremental approaches within a proven structured lifecycle. OpenUP is based on use cases and scenarios, risk management, and an architecture-centric approach to drive development[4]. OpenUP process, though complete in its target coverage and context, also serves as a base process upon which additional process content can be built. Plug-ins can extend OpenUP to include guidance for large-scale techniques (such as Model-Driven Development) and lighter, agile techniques (such as Agile Database Techniques). Tool vendors can create plug-ins that attach tool mentors to tasks giving step-by-step instructions on how the tool can be used within the context of the process. In addition to this community of plug-ins that can be mixed and matched to build a tailored process – and possibly more important for the goal of having a process that meets the specific needs of a particular project – the Eclipse Process Framework Composer tool can be used to author in-house content. Organization-specific templates can be integrated into the process content and new process elements from checklists and guidance to brand new roles, tasks, and work products can be introduced [4].
OpenUP Phases include:
Inception Phase Iteration[4]
In this phase, developers analyze the things that should be built, identify the system functionality, cost, schedule, risks.
Elaboration Phase Iteration[4]
This phase deals with the design, implementation, validation of an architecture, understanding of the requirements, and alleviation of possible risks that might occur.
Construction Phase Iteration[4]
Develop a complete product for its user community and minimize development cost to achieve some degree of parallelism
Transition Phase Iteration[4]
After the product is deployed, beta testing is needed to validate if user expectations are met and achieve stakeholder agreement that deployment is complete.
As a summary, OpenUP is a minimal, complete and extensible process. It fosters agile techniques and principles, while has a proven structured lifecycle that emphasizes the continuous delivery of quality software that is valuable to stakeholders.
References:
1. Jean-Michel de Jaeger. PMI - PMBOK guide (Third Edition 2004). Retrieved 29Nov09.
2. P. Fitsilis. Comparing PMBOK and Agile Project Management Software Development Processes. Retrieved from
3."Eclipse Process Framework Project". Eclipse. Retrieved from
4.Ricardo Balduino. Introduction to OpenUP. August 2007. Retrieved 29Nov09.
No comments:
Post a Comment