Explanation/Reference:
A lag is the amount of time whereby a successor activity will be delayed with respect to a predecessor activity.
For example, a technical writing team may begin editing the draft of a large document 15 days after they begin writing it.
Process: 6.3 Sequence Activities
Definition: The process of identifying and documenting relationships among the project activities.
Key Benefit: The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Milestone list
5. Project scope statement
6. Enterprise environmental factors
7. Organizational process assets
Tools & Techniques
1. Precedence diagramming method (PDM)
2. Dependency determination
3. Leads and lags
Outputs
1. Project schedule network diagrams
2. Project documents updates

Section: Volume E

Explanation/Reference:
Explanation:
5.2.3.1 Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project.
Requirements may start out at a high level and become progressively more detailed as more about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing an executive summary, detailed descriptions, and attachments.
Components of requirements documentation can include, but, are not limited to:
Business requirements, including:

○ Business and project objectives for traceability;
○ Business rules for the performing organization; and
○ Guiding principles of the organization
* Stakeholder requirements, including:
○ Impacts to other organizational areas;
○ Impacts to other entities inside or outside the performing organization; and
○ Stakeholder communication and reporting requirements.
* Solution requirements, including:
○ Functional and nonfunctional requirements;
○ Technology and standard compliance requirements;
○ Support and training requirements;
○ Quality requirements; and
○ Reporting requirements, etc. (solution requirements can be documented textually, in models, or both).
Project requirements, such as:

○ Levels of service, performance, safety, compliance, etc.; and
○ Acceptance criteria.
Transition requirements.

Requirements assumptions, dependencies, and constraints.