Showing posts from November, 2011

Requirements/Scope Management - Part 5. Mapping RUP Requirements Management to PMBoK Scope Management

IBM RUP is a prescriptive approach for software engineering best practices. PMI Guide to the PMBoK is a descriptive approach for project management best practices. RUP focuses on PM best practices in the context of software development and deployment projects while the PMBOK best practices are generic and applicable to management of projects in any application domain. In the other words, RUP PM Discipline is a specific instance of the PMBOK's generic PM best practices.

Requirements/Scope Management - Part 4. PMBoK Scope Management

Definitions Product Scope - the features and functions that are to be included in a product or service. Project Scope - the work required to deliver a product with specified features and functions. Processes Collect Requirements Define Scope Create WBS Verify Scope Control Scope

Requirements/Scope Management - Part 3. Introduction to PMBoK

What is PMBoK A Guide to the Project Management Body of Knowledge is a book published by Project Management Institute. It presents a set of standard terminology and guidelines for project management. The Third Edition (2004) was recognised as a standard by the Institute of Electrical and Electronics Engineers — IEEE 1490-2003. The Fourth Edition (2008) was recognized by the American National Standards Institute (ANSI) as an ANSI/PMI 99-001-2008.

Requirements/Scope Management - Part 2. RUP Requirements Management

Definitions Requirement is a condition or capability to which the system must conform. Requirements Management is a systematic approach to eliciting, organizing, and documenting the requirements of the system, or Requirements Management is a process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system. Why manage requirements Project success is defined by meeting project requirements: conformance to some set of requirements defines the success or failure of projects. Failing to manage requirements decreases the probability of meeting these objectives.

Requirements/Scope Management - Part 1. Introduction to RUP

What is RUP The Rational Unified Process is an iterative software development process framework created by the Rational Software Corporation. RUP is not a concrete process, but an adaptable process framework. It is to be adapted by the development organizations and teams that will select the elements of the process that are appropriate for their needs.