Depending on your processing style, you may take one or two steps to start building scope diagrams. If you tend to be more analytical and detailed, you may start with a table. If you are more visual and nonlinear as a thinker, you may skip this step and go straight to a picture. In either case, it might be best to try both just to figure out what works for you.
Either way, you are working to discover two things. First, who will provide necessary guidance to the project team while building the solution? Some people call these the inputs to the project. This may include some or all of the following questions:
- Who will provide the requirements—the specifications of what’s needed?
- Who will be writing the check for the work? Who manages the budget?
- Who will tell you what processes or standards need to be followed?
- Who will provide the technology needed?
- Who will provide the people you will need (and determine if you will need or get more)?
- Who will do the design work?
- Who will do the testing or compliance work?
Second, you will also ask yourself, “Who or what (for example, systems) will receive things from this project?” Some people call these the output of the project. This may include some or all of the following questions:
- To whom will the project deliver reports?
- Who will receive the final deliverables of the project?
- What systems will the project have to build interfaces with?
- Who will do the training for the rollout, and what do they need to do this?
- Who will do marketing and sales for the rollout, and what do they need to do this?