Documents – Page 4 – Memorres Information Center

WBS Quality Check

Purpose

The WBS Quality Check Checklist provides lean project teams with a structured method to validate that the Work Breakdown Structure (WBS) and its Dictionary meet the required standards of completeness, clarity, and alignment before being baselined. Its purpose is to ensure that Memorres projects have a sound planning foundation, where deliverables and work packages are unambiguous, traceable, and approved.

A poorly structured WBS leads to inaccurate estimates, unclear responsibilities, and uncontrolled scope creep. This checklist prevents such risks by giving Project Managers a repeatable verification process that confirms all requirements are represented, all deliverables are decomposed to a manageable level, and every work package is clearly described. For lean PM teams (1–3 members), this ensures efficiency by avoiding costly rework later in the project lifecycle.

By enforcing this quality gate, the checklist strengthens governance, ensures auditability in MIC, and provides sponsors with confidence that the WBS baseline is fit for estimation, resource planning, and scheduling.

Scope

This checklist applies to all projects managed by the Memorres Project Management Department and is mandatory during the Planning phase, after the WBS & Dictionary have been prepared and before estimates and schedules are finalized.

The scope of the checklist covers verification of structure, traceability, completeness, uniqueness, ownership, and approval of all WBS elements. It also confirms that assumptions, dependencies, and constraints linked to the WBS are documented in MIC.

The checklist excludes task-level engineering detail or technical design breakdowns, which belong to delivery teams. Responsibility for executing this checklist lies with the Project Manager, with oversight by the PMO and final approval from the Sponsor.

Main Section

Table: WBS Quality Check Checklist

Step	Action	Execution Guidance	Example/Evidence
1	Verify scope coverage	Cross-check that all requirements are represented in the WBS.	Requirement BR-001 mapped to WP-01.
2	Validate decomposition levels	Confirm deliverables are broken down to manageable, non-overlapping work packages.	“UI Wireframes” distinct from “Final UI Design.”
3	Check dictionary completeness	Ensure each work package has description, deliverables, acceptance criteria, dependencies, assumptions, and owner.	WP-02 entry includes acceptance criteria.
4	Confirm traceability	Link each WBS element back to scope statement and requirements.	Req-to-WBS matrix in MIC.
5	Test clarity	Confirm that work package titles and descriptions are unambiguous.	WP-03 titled “User Training Materials” with clear scope.
6	Validate uniqueness	Ensure no duplicate work packages exist.	WP-02 and WP-03 not overlapping.
7	Confirm ownership	Each work package has a named owner responsible for delivery.	Design Lead owns WP-02.
8	Check assumptions/dependencies	Ensure linked assumptions and dependencies are logged.	Assumption A-001 linked to WP-01.
9	Verify approval readiness	Confirm stakeholders reviewed and Sponsor is ready to sign-off.	Draft circulated, feedback resolved.
10	Archive evidence	Store WBS, Dictionary, and checklist in MIC before baseline approval.	Folder “Project X/WBS v1.0” complete.

Closing Note & Cross-References

The WBS Quality Check Checklist ensures Memorres projects do not move into estimation, resource planning, or scheduling with incomplete or unclear scope structures. It provides lean PM teams with a lightweight but disciplined quality gate, strengthening governance and preventing downstream rework.

Resource Plan & Skill Map

Purpose

The Resource Plan & Skill Map Template provides a standardized format for documenting the resources required to deliver each work package in the WBS, along with the skills needed and availability commitments. Its purpose is to ensure lean PM teams (1–3 members) can allocate resources effectively, avoid overloads, and confirm that the right expertise is available at the right time.

Projects often face delays or quality issues not because of poor planning, but because resource skills were mismatched or availability was assumed rather than validated. This template prevents those risks by combining a resource allocation register with a skill competency map. It allows Project Managers to match tasks with capabilities, identify gaps early, and engage sponsors or HR for resource augmentation where needed.

For Memorres, where teams are lean and multitasking is common, this template ensures resource planning is evidence-based, auditable, and aligned with approved estimates. It also provides sponsors with visibility into resource commitments, reducing conflicts across parallel projects. Once approved, the Resource Plan & Skill Map serves as the baseline for schedule development and workload tracking.

Scope

This template applies to all Memorres projects during the Planning phase, after the WBS & Dictionary and Effort & Duration Estimation Sheet are completed. It is mandatory for projects requiring cross-functional collaboration or external vendor involvement.

The scope includes:

Mapping each work package to specific resources.
Recording skills required for each task.
Documenting resource allocation (hours/days) against availability.
Identifying skill gaps and escalation requirements.

The template excludes HR-level role descriptions or staffing contracts, which are managed separately. Responsibility for completing the Resource Plan rests with the Project Manager. Resource owners and stakeholders must confirm availability, and the Sponsor/PMO must approve the plan before scheduling begins.

Main Section

Table 1: Header Fields

Field	Description	Example
Project Title	Name of the project	“Client Portal Modernization”
Resource Plan Version	Document version	v1.0
Prepared By	Project Manager	[PM Name]
Date	Date of preparation	24-Sep-2025
Approved By	Sponsor/PMO	[Sponsor Name]
Approval Date	Date of approval	26-Sep-2025

Table 2: Resource Allocation Register

WBS ID	Work Package Title	Resource Name	Role	Allocation (Person-Hours/Days)	Availability Confirmed (Yes/No)	Example
1.1	Requirements Baseline	[PM Name]	Project Manager	40 hrs	Yes	PM leading workshops
1.2.1	UI Wireframes	[Designer Name]	Design Lead	32 hrs	Yes	Wireframes for all modules
1.2.2	Final UI Design	[Designer Name]	Design Lead	60 hrs	No	Pending approval for extension
1.3	User Training Materials	[Trainer Name]	Training Coordinator	40 hrs	Yes	Manuals + guides

Table 3: Skill Map

Resource Name	Role	Key Skills	Competency Level (Basic/Intermediate/Advanced)	Gap Identified	Example
[Designer Name]	Design Lead	UI/UX design, wireframing tools	Advanced	None	Figma expert
[Trainer Name]	Training Coordinator	Technical writing, instructional design	Intermediate	Needs SME support	Writing strong, SME gaps
[PM Name]	Project Manager	Stakeholder management, requirements analysis	Advanced	None	Experienced PM

Table 4: Approval Record

Approver	Role	Signature/Date	Example
[Sponsor Name]	Project Sponsor	[Signed 26-Sep-2025]	CIO sign-off
[PM Name]	Project Manager	[Signed 24-Sep-2025]	PM signature

Closing Note & Cross-References

The Resource Plan & Skill Map Template ensures every work package is matched with committed resources and verified skills. For lean Memorres teams, this artifact is critical for avoiding overloads, clarifying ownership, and identifying gaps early. Once approved, it serves as the baseline for schedule development and workload tracking.

Effort & Duration Estimation Sheet

Purpose

The Effort & Duration Estimation Sheet Template provides a standardized format for documenting and validating work package estimates in Memorres projects. Its purpose is to ensure lean PM teams (1–3 members) can capture realistic effort (person-hours/days) and duration (calendar time) for each WBS element in a transparent and auditable manner.

Estimation errors are a major cause of project overruns. Overly optimistic estimates result in missed deadlines, while inflated estimates lead to resource inefficiency and sponsor mistrust. This template mitigates those risks by combining structured estimation practices with ownership, assumptions, and approval records. It supports Project Managers in making defensible commitments and facilitates better scheduling, resource planning, and risk management.

For Memorres, where projects run with lean resources and compressed timelines, this template ensures every estimate is tied to a specific WBS work package, validated against assumptions, and aligned with the chosen estimation method (Expert, Analogous, or 3-Point). It also provides visibility for sponsors and PMO, enabling oversight and governance of the estimation process.

Scope

This template applies to all projects managed by the Memorres Project Management Department. It is mandatory during the Planning phase, after the WBS & Dictionary are approved and before schedules or resource plans are finalized.

The scope of this template includes capturing effort and duration estimates for every work package, recording the estimation method used, identifying assumptions or constraints, and documenting ownership and approval. It ensures that all estimates are evidence-based and traceable.

The template excludes detailed engineering estimates (e.g., agile story-points, technical sizing models), which are team-specific practices. Responsibility for maintaining this sheet lies with the Project Manager. SMEs and stakeholders provide inputs, while the Sponsor/PMO validates and approves estimates before baseline schedules are developed.

Main Section

Table 1: Header Fields

Field	Description	Example
Project Title	Name of the project	“Client Portal Modernization”
Estimation Version	Document version	v1.0
Prepared By	Project Manager	[PM Name]
Date	Date of preparation	22-Sep-2025
Approved By	Sponsor/PMO	[Sponsor Name]
Approval Date	Date of approval	24-Sep-2025

Table 2: Effort & Duration Estimation Register

WBS ID	Work Package Title	Estimation Method (Expert/Analogous/3-Point)	Effort Estimate (Person-Hours/Days)	Duration Estimate (Calendar Days)	Assumptions/Constraints	Owner	Status	Example
1.1	Requirements Baseline	Expert	80 hrs	10 days	SME availability confirmed	PM	Approved	Req Spec in 2 weeks
1.2.1	UI Wireframes	3-Point (O=20, M=30, P=50 → 32 hrs)	32 hrs	5 days	Assumes timely feedback	Design Lead	In Progress	Wireframes draft in 5 days
1.2.2	Final UI Design	Analogous	60 hrs	7 days	Based on past portal project	Design Lead	Planned	Mockups approved in 7 days
1.3	User Training Materials	Expert	40 hrs	6 days	Assumes access to SMEs	Training Coordinator	Not Started	Manuals delivered Q4

Table 3: Approval Record

Approver	Role	Signature/Date	Example
[Sponsor Name]	Project Sponsor	[Signed 24-Sep-2025]	CIO sign-off
[PM Name]	Project Manager	[Signed 22-Sep-2025]	PM signature

Closing Note & Cross-References

The Effort & Duration Estimation Sheet Template ensures that all work package estimates are documented, validated, and approved before baseline schedules are developed. It provides lean PM teams with a lightweight yet disciplined tool to manage estimation governance. Once signed-off, this sheet must be stored in MIC and referenced throughout planning and control.

Estimation Practices (Expert, Analogous, 3-Point)

Purpose

The purpose of this guide is to provide lean Project Managers with practical, repeatable methods for estimating effort and duration of work packages defined in the WBS. Estimation is one of the most challenging aspects of project planning, especially in lean teams (1–3 members) where resources are limited, and overruns have significant impacts. This guide equips PMs with three proven techniques—Expert Judgment, Analogous Estimation, and 3-Point Estimation—that can be applied consistently across Memorres projects.

The guide balances simplicity with rigor. It avoids over-engineered estimation methods unsuitable for lean teams but ensures enough structure to produce defensible estimates. By applying these techniques, Project Managers can develop realistic plans, reduce the risk of over-promising, and provide sponsors with transparent reasoning for effort and timeline commitments.

Scope

This guide applies to all Memorres projects during the Planning phase, after the WBS & Dictionary are completed and before baseline schedules are approved. It covers estimation practices at the governance level, ensuring that each work package has an evidence-based estimate of effort and/or duration.

The scope includes:

Explaining three estimation methods (Expert, Analogous, 3-Point).
Providing guidance on when and how to use each method.
Offering examples relevant to software/digital transformation projects.
Linking estimation practices to downstream documents (estimation sheets, schedules, resource plans).

The guide does not prescribe detailed engineering estimates or agile story-pointing, which are delivery-level practices. Responsibility for applying these practices rests with the Project Manager, with inputs from SMEs, stakeholders, and PMO oversight.

Main Section

Table 1: Estimation Methods Overview

Estimation Method	Principle	Application Guidance	Example
Expert Judgment	Relies on the knowledge of experienced SMEs or project managers.	Use when domain expertise is available; document rationale; cross-check with historical data.	SME estimates 40 hours for module design based on prior experience.
Analogous Estimation	Uses historical data from similar past projects.	Best for early-stage estimates; requires access to MIC records or prior project data.	Past portal redesign took 300 hours; current project estimated at 280–320 hours.
3-Point Estimation	Considers optimistic (O), pessimistic (P), and most likely (M) estimates to calculate expected effort using (O + 4M + P)/6.	Use when uncertainty exists; documents variability; helps communicate risk.	O = 20 hrs, M = 30 hrs, P = 50 hrs → Expected = 32 hrs.

Narrative Guidance

Expert Judgment

Expert judgment is efficient for lean teams where SMEs have deep experience with similar projects. The PM must ensure the rationale is documented to avoid reliance on undocumented assumptions. Expert estimates should be validated against WBS Dictionary deliverables and, where possible, cross-checked with historical MIC data.

Analogous Estimation

Analogous estimation is most useful when little detail is available. By comparing to past projects of similar scope, PMs can provide early estimates that are realistic and defensible. This method requires a strong knowledge base in MIC and disciplined recordkeeping from prior projects. While less precise than other methods, it provides quick directional estimates.

3-Point Estimation

3-Point Estimation is effective when uncertainty is high or when work packages are influenced by external dependencies. By capturing optimistic, most likely, and pessimistic values, PMs communicate the range of possible outcomes and quantify risk. This method is especially suitable for projects involving integrations, vendor dependencies, or first-time activities.

Closing Note & Cross-References

The Estimation Practices Guide ensures Memorres projects apply structured, transparent, and repeatable estimation methods rather than ad hoc guesses. Lean PM teams should select the most appropriate method for each work package based on available data and uncertainty. Once estimates are derived, they must be recorded in the Effort & Duration Estimation Sheet, linked to the WBS Dictionary, and validated with stakeholders before baselining.

Work Breakdown Structure (WBS) & Dictionary

Purpose

The combined WBS & Dictionary Template provides a single, authoritative format for defining and describing the scope of Memorres projects. It ensures lean project teams (1–3 members) can both decompose the project into a hierarchical WBS and document the details of each work package in one place.

The WBS shows how project scope is structured into deliverables and work packages, while the Dictionary provides detailed descriptions, deliverables, acceptance criteria, dependencies, assumptions, ownership, and status. By merging these two into one template, lean PM teams reduce duplication, improve clarity, and maintain a single source of truth for planning, estimation, and resource allocation.

This template prevents scope gaps, overlaps, or misinterpretations. It creates traceability from requirements to deliverables, supports accountability through ownership assignments, and provides auditable evidence of scope baseline approval. Once approved, the WBS & Dictionary must be archived in MIC and serve as the foundation for estimation, scheduling, and monitoring.

Scope

This template applies to all projects managed by the Memorres Project Management Department and is mandatory during the Planning phase after scope approval. It must be completed before estimates, resource plans, and baseline schedules are created.

The scope of this template includes:

Structuring project scope into hierarchical levels (WBS).
Documenting detailed dictionary entries for each work package.
Recording ownership, acceptance criteria, dependencies, and assumptions.
Capturing approvals for the scope baseline.

It excludes detailed engineering task lists or technical design specifications, which belong to delivery teams. The Project Manager owns this template, stakeholders provide validation of specific work packages, and the Sponsor/PMO approve the final baseline.

Main Section

Table 1: Header Fields

Field	Description	Example
Project Title	Name of the project	“Client Portal Modernization”
WBS Version	Version number	v1.0
Prepared By	Project Manager	[PM Name]
Date	Date of preparation	18-Sep-2025
Approved By	Sponsor/PMO	[Sponsor Name]
Approval Date	Date of approval	20-Sep-2025

Table 2: WBS & Dictionary Register

WBS ID	Level	Parent ID	Title	Description	Deliverables	Acceptance Criteria	Dependencies	Assumptions	Owner	Status	Example
1.0	1	–	Client Portal Modernization	Entire project scope	Approved portal	Sponsor acceptance	None	Scope approved	Project Manager	Approved	Overall program
1.1	2	1.0	Requirements Baseline	Capture and validate requirements	Requirements Spec v1.0	Signed-off by stakeholders	Depends on SME availability	Assumes SME time provided	PM	Approved	Req Spec signed 12-Sep-2025
1.2	2	1.0	Portal Redesign	Redesign user interface	Approved UI mockups	Sponsor sign-off	Depends on requirements baseline	Assumes design tools available	Design Lead	In Progress	Wireframes in review
1.2.1	3	1.2	UI Wireframes	Develop module-level wireframes	Draft wireframes	Stakeholder approval	Requires validated requirements	Assumes timely SME review	Design Lead	In Progress	Wireframes submitted 17-Sep-2025
1.2.2	3	1.2	Final UI Design	Deliver high-fidelity mockups	Final mockups	Sponsor sign-off	Depends on wireframes	Assumes no major scope change	Design Lead	Not Started	Planned for Oct 2025
1.3	2	1.0	User Training	Develop training materials	Training docs & guides	SME validation	Depends on portal completion	Assumes SME feedback	Training Coordinator	Not Started	Planned for Q4 2025

Table 3: Approval Record

Approver	Role	Signature/Date	Example
[Sponsor Name]	Project Sponsor	[Signed 20-Sep-2025]	CIO sign-off
[PM Name]	Project Manager	[Signed 18-Sep-2025]	PM signature

Closing Note & Cross-References

The WBS & Dictionary Template ensures that project scope is both structured and described in a single document, reducing complexity for lean teams. By combining hierarchical breakdown with detailed descriptions, it provides the baseline for estimation, scheduling, resource allocation, and monitoring. Once signed-off, this register must be stored in MIC as the official scope baseline.

WBS Development & Dictionary

Purpose

The purpose of this SOP is to provide a structured, repeatable process for developing the Work Breakdown Structure (WBS) and accompanying WBS Dictionary in Memorres projects. For lean PM teams (1–3 members), the WBS is the foundation of project planning, translating approved requirements and scope into manageable, traceable work packages. The WBS Dictionary supplements this by describing each element in detail, ensuring clarity across all stakeholders.

Without a WBS, projects risk fragmented planning, unclear responsibilities, and poor cost or effort tracking. This SOP mitigates those risks by defining how PMs should decompose project scope, structure deliverables, and validate completeness. The WBS acts as the backbone for estimation, scheduling, resource planning, and progress tracking.

The WBS Dictionary complements the structure by clarifying scope, deliverables, acceptance criteria, and ownership for each work package. This ensures traceability back to requirements, avoids duplication of effort, and provides auditable evidence for governance. Together, they prevent scope creep, facilitate accountability, and enable lean PM teams to control projects effectively.

Scope

This SOP applies to all projects managed under the Memorres Project Management Department and is mandatory during the Planning phase, following the approval of requirements and scope. It covers the decomposition of project deliverables into a hierarchical WBS, the preparation of a WBS Dictionary, and the validation of completeness and alignment.

The SOP excludes detailed engineering task breakdowns or technical solution design, which are delivery responsibilities. Instead, it focuses on governance and planning: ensuring that every requirement is captured in the WBS and that each work package is defined with clarity.

The Project Manager owns the creation and maintenance of the WBS and Dictionary. Sponsors approve the overall WBS, stakeholders validate their respective work packages, and the PMO ensures compliance with MIC standards.

Main Section

Table 1: RACI – WBS Development & Dictionary Activities

Activity	Project Manager	Sponsor	Stakeholders	PMO	Example
Develop draft WBS	R	I	C	I	PM drafts WBS from scope
Validate coverage against requirements	R	I	A	C	SME checks deliverables covered
Prepare WBS Dictionary entries	R	I	C	I	PM documents work package details
Review and refine	R	C	A	I	Stakeholder confirms accuracy
Approve WBS & Dictionary	C	A	C	R	Sponsor signs baseline

Table 2: Workflow – WBS Development & Dictionary

Step	Inputs	PM Activities	Outputs	Gate Criteria	Example
1	Approved Scope Statement	Break scope into high-level deliverables	Draft WBS Level 1	All scope elements represented	Portal redesign, integrations
2	Validated Requirements	Decompose deliverables into work packages	WBS Level 2–3	No requirements unlinked	Onboarding workflow → module tasks
3	Draft WBS structure	Document work package details in Dictionary	Draft Dictionary entries	All work packages described	ID, owner, acceptance criteria included
4	Draft WBS + Dictionary	Circulate for stakeholder review	Reviewed WBS & Dictionary	Conflicts resolved	Duplicate packages removed
5	Reviewed WBS & Dictionary	Secure sponsor & PMO approval	Approved baseline	Sign-off recorded in MIC	WBS v1.0 approved 18-Sep-2025

Table 3: Quality Checklist

Criterion	Test	Evidence	Example
Completeness	All requirements mapped to WBS	Traceability matrix	Req BR-001 mapped to WP-01
Clarity	Each work package described unambiguously	WBS Dictionary entries	“User Training Material Development”
Uniqueness	No duplicate or overlapping work packages	Cross-check review	WP-02 and WP-03 distinct
Alignment	WBS aligns with Scope Statement and Charter	Document comparison	Scope v1.0 vs. WBS v1.0
Approval	Sponsor sign-off documented	Signed baseline in MIC	Sponsor signed 18-Sep-2025

Closing Note & Cross-References

The WBS Development & Dictionary SOP ensures that Memorres projects translate scope into clear, manageable work packages with documented ownership and acceptance criteria. The WBS becomes the backbone for estimation, scheduling, and reporting, while the Dictionary ensures each element is unambiguous. Both must be approved, version-controlled, and archived in MIC before detailed planning proceeds.

Requirements Walkthrough & Approval

Purpose

The Requirements Walkthrough & Approval Checklist provides lean project teams with a structured, step-by-step mechanism to ensure that validated requirements are reviewed, agreed upon, and formally signed off by all relevant stakeholders. Its purpose is to reduce the risk of incomplete validation, overlooked requirements, or misalignment between business needs and delivery scope.

For Memorres projects, where PM teams are small (1–3 members) and client expectations are often dynamic, the walkthrough process ensures clarity and agreement before scope baselines are finalized. It also provides a governance safeguard by requiring explicit approvals rather than relying on informal confirmations. This checklist standardizes the walkthrough process, ensuring that every requirement is traceable, every assumption is tested, and every stakeholder acknowledges the project’s direction.

By following this checklist, Project Managers prevent scope creep, avoid disputes during execution, and maintain a defensible audit trail in MIC. It helps sponsors and stakeholders clearly understand what will be delivered, under what constraints, and how success will be measured.

Scope

This checklist applies to all projects managed under the Memorres Project Management Department and is mandatory before the Requirements Specification is baselined. It covers the walkthrough process from scheduling review sessions, preparing validation material, conducting structured walkthroughs, resolving conflicts, and recording approvals.

The checklist does not prescribe technical reviews of detailed designs or engineering specifications. Instead, it focuses on governance: ensuring requirements are complete, testable, aligned with objectives, and approved by authorized stakeholders.

Responsibility for executing this checklist lies with the Project Manager, who must schedule walkthroughs, record feedback, and secure sign-offs. Stakeholders are responsible for providing timely review and clarification, while the Sponsor and PMO confirm final approval.

Main Section

Table: Requirements Walkthrough & Approval Checklist

Step	Action	Execution Guidance	Example/Evidence
1	Schedule Walkthrough Session	Confirm date/time with sponsor and key stakeholders; circulate agenda.	Agenda sent to all stakeholders 7 days before meeting.
2	Prepare Requirements Package	Consolidate requirements into the approved template with traceability and assumptions.	Requirements Spec v1.0 attached in MIC.
3	Circulate Requirements in Advance	Share draft at least 3 working days before walkthrough; highlight open items.	Draft requirements shared with SMEs on 10-Sep-2025.
4	Conduct Walkthrough Meeting	Review requirements line by line; capture clarifications, conflicts, or corrections.	Meeting minutes recorded, attendance list attached.
5	Resolve Conflicts	Consolidate feedback, resolve discrepancies, and re-circulate updated draft.	Duplicate requirement removed after SME input.
6	Validate Testability	Ensure every requirement has measurable acceptance criteria.	“Upload within 3 clicks” criteria confirmed.
7	Secure Stakeholder Sign-Off	Obtain signatures from all key stakeholders.	Signed approval page dated 12-Sep-2025.
8	Obtain Sponsor/PMO Approval	Sponsor provides final sign-off; PMO archives version in MIC.	Sponsor sign-off recorded in MIC on 14-Sep-2025.
9	Archive Evidence	Store requirements, approval record, and meeting minutes in MIC.	Folder “Project X/Requirements Baseline” complete.
10	Confirm Readiness for Scope Baseline	Ensure requirements are approved and linked to scope statement.	Requirements linked to Scope v1.0 in MIC.

Closing Note & Cross-References

The Requirements Walkthrough & Approval Checklist ensures Memorres projects do not proceed to scope baselining without clear, validated, and approved requirements. It provides lean PM teams with a repeatable quality gate, reducing risks of disputes or rework. All walkthrough evidence—including minutes, approvals, and signed requirements—must be archived in MIC.

Scope Statement & Out-of-Scope Definition

Purpose

The purpose of this SOP is to establish a structured process for defining, documenting, and approving the project scope at Memorres. It ensures lean PM teams (1–3 members) can clearly articulate what is included in the project (in-scope) and what is excluded (out-of-scope). This explicit definition prevents scope creep, misaligned expectations, and disputes during delivery.

Projects often fail not because of technical shortcomings, but because stakeholders and delivery teams interpret the scope differently. This SOP provides Project Managers with a repeatable, evidence-based process to define boundaries, secure sponsor approval, and maintain discipline throughout the lifecycle. It links requirements to objectives, documents exclusions, and clarifies assumptions or constraints that directly influence scope.

By enforcing scope clarity early, lean teams can conserve bandwidth, plan effectively, and protect delivery timelines. The SOP also ensures that any future changes to scope are processed through the Change Request & Scope Control Policy, safeguarding governance while enabling controlled adaptability.

Scope

This SOP applies to all projects managed under the Memorres Project Management Department. It is mandatory during the Requirements & Scope Baseline phase, after requirements have been elicited and validated. The SOP covers the preparation of the Scope Statement, identification of in-scope deliverables, explicit recording of out-of-scope items, and the process for obtaining approvals.

The SOP excludes engineering-level design documentation or task-level WBS creation, which are addressed in planning documents. Instead, it focuses on governance and clarity: identifying what the project will deliver, what it will not deliver, and how these boundaries are approved and controlled.

The Project Manager is responsible for preparing and maintaining the Scope Statement. Sponsors must approve scope boundaries, while stakeholders are accountable for reviewing inclusions and exclusions. The PMO ensures compliance with MIC standards and cross-checks consistency against requirements and assumptions.

Main Section

Table 1: RACI – Scope Definition Activities

Activity	Project Manager	Sponsor	Stakeholders	PMO	Example
Draft Scope Statement	R	C	C	I	PM prepares initial draft
Define In-Scope Deliverables	R	A	C	I	Portal redesign included
Define Out-of-Scope Items	R	A	C	I	Mobile app explicitly excluded
Validate Scope with Stakeholders	R	C	A	I	Workshop review completed
Approve Scope Statement	C	A	C	R	Sponsor sign-off, PMO records

Table 2: Workflow – Scope Statement & Out-of-Scope Definition

Step	Inputs	PM Activities	Outputs	Gate Criteria	Example
1	Validated requirements, Charter	Draft initial Scope Statement	Draft scope document	All requirements covered	Draft lists portal features
2	Requirements, assumptions	Define in-scope deliverables	In-scope list	Matches objectives in Charter	Onboarding module included
3	Assumptions, constraints	Define out-of-scope items	Exclusion list	Explicitly documented	Mobile app excluded
4	Draft scope doc	Circulate to stakeholders	Reviewed scope document	No conflicts raised	SME review complete
5	Reviewed scope doc	Present to Sponsor/PMO	Approved Scope Statement	Sign-off recorded	Scope v1.0 signed 15-Sep-2025

Table 3: Quality Checklist

Criterion	Test	Evidence	Example
Completeness	All validated requirements addressed	Scope statement cross-check	Requirements-to-scope matrix
Clarity	Inclusions and exclusions are unambiguous	No overlaps or vague items	“Mobile app excluded”
Alignment	Scope matches objectives in Charter	Traceability matrix	Objective: faster onboarding linked to scope
Approval	Sponsor sign-off captured	Signed Scope Statement in MIC	v1.0 signed on 15-Sep-2025

Closing Note & Cross-References

The Scope Statement & Out-of-Scope Definition SOP provides lean PM teams with a disciplined method to set project boundaries and secure sponsor alignment. Once approved, the Scope Statement becomes the baseline for planning and delivery. Any future changes to scope must follow the Change Request & Scope Control Policy, ensuring governance and auditability.

Template – Assumptions & Constraints Log

Purpose

The Assumptions & Constraints Log Template provides a structured format for capturing, reviewing, and monitoring the underlying conditions that shape project execution. Its purpose is to ensure lean PM teams (1–3 members) can explicitly document factors that are accepted as true (assumptions) and factors that restrict or limit choices (constraints). By recording these elements early and monitoring them throughout the lifecycle, Project Managers reduce ambiguity, manage risk proactively, and prevent untested assumptions from derailing the project.

Many projects fail not because of flawed execution, but because key assumptions proved false or constraints were underestimated. This template mitigates that risk by making all critical conditions visible, testable, and traceable. It also supports informed decision-making during planning and scope control by distinguishing between negotiable assumptions and non-negotiable constraints.

For Memorres projects, where teams often operate with lean resources, the ability to quickly validate assumptions and plan around constraints is essential. This template provides a repeatable structure that ensures accountability by assigning ownership and status to each entry. It also enables sponsors and stakeholders to challenge or validate project conditions before committing resources.

Scope

This template applies to all projects managed by the Memorres Project Management Department. It is mandatory during the Requirements & Scope Baseline phase and must be completed alongside the Requirements Specification. The log must be updated throughout the project lifecycle whenever assumptions change or new constraints are identified.

The scope of this template includes recording business, technical, operational, and external assumptions, as well as fixed constraints such as budget caps, deadlines, compliance obligations, or resource limits. It supports planning, risk management, and change control by linking each entry to objectives and monitoring methods.

The template excludes detailed technical limitations or solution-specific design constraints, which are owned by delivery teams. The Project Manager is responsible for maintaining the log, with stakeholders accountable for validating assumptions and sponsors accountable for approving constraints that impact budget, scope, or schedule.

Main Section

Table 1: Header Fields

Field	Description	Example
Project Title	Name of the project	“Client Portal Modernization”
Version	Document version	v1.0
Prepared By	Project Manager	[PM Name]
Date	Date of preparation	12-Sep-2025
Approved By	Sponsor/PMO	[Sponsor Name]
Approval Date	Date of sign-off	14-Sep-2025

Table 2: Assumptions & Constraints Log

ID	Type (Assumption/Constraint)	Description	Impact if Invalid	Validation/Monitoring Method	Owner	Status	Example
A-001	Assumption	Client will provide SMEs for requirements workshops	Delays in capturing requirements	Confirm SME availability via email before workshops	Project Manager	Open	SME confirmation requested
A-002	Assumption	Third-party APIs will be stable and accessible	Integration delays if unstable	Validate via test calls before development	Tech Lead	Open	API test scheduled
C-001	Constraint	Project must complete by 30-Nov-2025	Cannot extend schedule beyond date	Monitor schedule variance weekly	Sponsor	Approved	Deadline fixed by contract
C-002	Constraint	Budget capped at 300 hours effort	Cannot exceed resource allocation	Monitor hours via time tracking policy	PMO	Approved	Budget envelope logged

Table 3: Approval Record

Approver	Role	Signature/Date	Example
[Sponsor Name]	Project Sponsor	[Signed 14-Sep-2025]	CIO sign-off
[PM Name]	Project Manager	[Signed 12-Sep-2025]	PM sign-off

Closing Note & Cross-References

The Assumptions & Constraints Log Template ensures that project teams do not rely on undocumented conditions or overlook critical restrictions. It provides visibility, accountability, and monitoring for factors that directly influence project feasibility and planning. By requiring explicit documentation, ownership, and status tracking, the template safeguards projects against surprises and unmanaged risks.

Template – Requirements Specification

Purpose

The Requirements Specification Template (PM Format) provides a structured approach for documenting, reviewing, and approving project requirements at Memorres. Its purpose is to create a single authoritative baseline that captures business, functional, and non-functional needs in a format that is traceable, reviewable, and manageable by lean PM teams (1–3 members).

Incomplete or ambiguous requirements are the most common cause of scope creep, cost overruns, and project delays. This template prevents those risks by consolidating requirements into one structured register where every item is linked to objectives, categorized, and validated with acceptance criteria. By merging business, functional, non-functional, and traceability elements into a single view, the template simplifies governance, reduces duplication, and provides clarity for sponsors and stakeholders.

Unlike technical specifications owned by engineering or QA teams, this PM-format document focuses on the “what” and “why,” not the “how.” It ensures that scope boundaries and success measures are captured clearly, so delivery and quality teams can design solutions that align with business intent.

Scope

This template applies to all projects managed under the Memorres Project Management Department. It is mandatory during the Requirements & Scope Baseline phase and must be completed before detailed planning begins.

The scope of this template includes capturing business needs, functional requirements, and non-functional constraints, along with their acceptance criteria, ownership, and approval status. It serves as the reference point for scope validation, planning, and change management throughout the lifecycle.

This template excludes engineering-level design specifications and detailed test cases. It is owned by the Project Manager and must be validated by stakeholders, with approval by the Sponsor or PMO. Once signed off, it becomes the baseline for planning and change control.

Main Section

Table 1: Header Fields

Field	Description	Example
Project Title	Name of the project	“Client Portal Modernization”
Version	Document version	v1.0
Prepared By	Project Manager	[PM Name]
Date	Date of preparation	10-Sep-2025
Approved By	Sponsor/PMO	[Sponsor Name]
Approval Date	Date of sign-off	12-Sep-2025

Table 2: Consolidated Requirements Register

ID	Requirement Type (BR/FR/NFR)	Requirement Description	Linked Objective	Acceptance Criteria	Owner	Priority	Status	Approval Sign/Date	Example
BR-001	Business	System must reduce client onboarding time	Objective 1 – Faster onboarding	20% reduction measured in process metrics	Sponsor	High	Approved	[Signed 12-Sep-2025]	Reduced onboarding from 15 → 12 days
FR-001	Functional	Portal must allow secure document uploads	Objective 2 – Improved usability	Upload completes within 3 clicks, encryption enabled	Tech Lead	High	In Review	Pending	Secure upload tested
NFR-001	Non-Functional	System must support 200 concurrent users	Objective 3 – Scalable operations	Stress-tested at 200 sessions	PMO	Medium	Open	Pending	Load test passed at 200 users
A-001	Assumption	APIs will be delivered within 2 weeks	Dependency on vendor	Confirmed delivery in writing	Vendor Manager	Critical	Open	Pending	API ETA 15-Sep-2025
D-001	Dependency	Test environment setup by vendor	Blocks testing phase	Delivered before UAT start	Vendor Manager	High	Open	Pending	Awaiting setup

Closing Note & Cross-References

The consolidated Requirements Specification Register provides a single, traceable view of all project requirements, covering business, functional, non-functional, assumptions, and dependencies. By merging them into one table, lean PM teams can maintain clarity without managing multiple disconnected documents. Once approved, this register becomes the scope baseline and must be stored in MIC for governance and audit.