One of the first things to do when you start a new project is to work out what it actually involves. As well as all the workshops about requirements and the documentation that results, there are some other things to investigate as part of your project scope.
Sit down with your project sponsor or other key users on the project and go through this checklist of 7 questions you should be asking about your project scope. They’ll appreciate that you have taken the time to ask and you’ll get a much better understanding of what they are expecting the project to deliver on their behalf.
Testing is a key part of nearly every successful project. But do you know the difference between a testing strategy and a test plan? This article provides some great detail in defining the roles of both.
A Test Strategy document is a high level document and normally developed by project manager. This document defines “Software Testing Approach” to achieve testing objectives. The Test Strategy is normally derived from the Business Requirement Specification document.
The Test Strategy document is a static document meaning that it is not updated too often. It sets the standards for testing processes and activities and other documents such as the Test Plan draws its contents from those standards set in the Test Strategy Document.
Some companies include the “Test Approach” or “Strategy” inside the Test Plan, which is fine and it is usually the case for small projects. However, for larger projects, there is one Test Strategy document and different number of Test Plans for each phase or level of testing.
What do people mean when they talk about the “project management lifecycle”? This helpful article, originally posted by Villanova University, explains in detail the five phases that projects are broken into throughout their life, when executed using the PMBOK methodology.
At the start of a project, the amount of planning and work required can seem overwhelming. There may be dozens, or even hundreds of tasks that need to be completed at just the right time and in just the right sequence.
Seasoned project managers know it is often easier to handle the details of a project and take steps in the right order when you break the project down into phases. Dividing your project management efforts into these five phases can help give your efforts structure and simplify them into a series of logical and manageable steps.