Completing scope Verification

During the planning phase of every project management process, project managers the world over create a scope management plan this plan details how you define your software project scope and declares how the project scope should be controlled to prevent scope creep. In your scope management plan, you must also record how you will verify your scope. Indeed, in the quality planning stage, you describe how the software would be formally accepted by the appropriate stakeholders. Your firm may...

Creating a Work Breakdown Structure

A work breakdown structure (WBS) is a visual representation of everything the project will create. Typically, a WBS includes things (deliverables, components, and so on), not activities. However, there's no hard-and-fast rule on exempting activities from your WBS. I prefer to keep work out of the WBS and focus on the things the work will create. Although we do allow some actions to sneak in, such as testing, ordering, and compiling, most of our WBSs are comprised of deliverables. And I know you...

Establishing project goals

Before you establish the project goals for your software project, you should become familiar with the goals of the organization. A good software project plan supports and aligns with the strategic goals of the organization. After you define the project goals, all of the other project management processes should support those goals. For example, the quality management plan should support the quality goals of the software project and the product. Have you ever heard the expression, If you don't...