0% found this document useful (0 votes)
4 views5 pages

Burger blocks

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views5 pages

Burger blocks

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Burger blocks

Target Completion Completion


Milestone Owner Status
Date Month

Development
Template Set-Up (Phase 1) 25 Nov November Complete
Team

Filtering/Pagination (Phase Development


30 Nov November In progress
1) Team

Development
SEO & Analytics (Phase 1) 5 Dec December Not started
Team

Visual QA (Phase 2) 15 Dec December QA Team Not started

Platform
PC QA Fixes (Phase 2) 20 Dec December Not started
Consultant

Client QA Fixes (Phase 3) 10 Jan January QA Team Not started

Development
Deployment (Phase 3) 15 Jan January Not started
Team

Development
Search Locator Frontend 20 Jan January Not started
Team

Development
Search Locator Backend 30 Jan January Not started
Team

MoSCoW Prioritization

Must-Have Tasks (Critical for project completion):


 These tasks are non-negotiable and are required to meet the client’s primary requirements.

Phase 1:

 Template Setup, Teaser Card, General Styling (14 hours)

 Filtering, Active Filter Labels, Pagination (10 hours)

Phase 2:

 Visual QA (5 hours)

Phase 3:

 Client QA Fixes (4 hours)

 Deployment (1 hour)

Should-Have Tasks (Important but not critical for immediate delivery):

 These tasks add value and quality to the project but can be deprioritized slightly.

Phase 1:

 SEO, Analytics, and Developer Self QA (11 hours)

Search Locator Enhancements:

 Frontend Updates (8 hours)

Could-Have Tasks (Nice-to-have but can be deferred):

 These tasks are optional and can be planned for future enhancements if time allows.

Search Locator Enhancements:

 Backend Configuration (12 hours)

Won’t-Have Tasks (Not included for now):

 These are tasks explicitly out of scope due to time and resource limitations.

o Any additional enhancements or new requirements outside the current scope.

Here's the table, incorporating both the milestones and estimated efforts in hours for each phase:
Target
Completion
Milestone Completion Owner Status Estimated Hours
Month
Date

14 hours
Template Set-Up Development
25 Nov November Complete (Execution Group
(Phase 1) Team
1)

10 hours
Filtering/Pagination Development In
30 Nov November (Execution Group
(Phase 1) Team progress
1)

11 hours
SEO & Analytics (Phase Development Not
5 Dec December (Execution Group
1) Team started
1)

5 hours
Not
Visual QA (Phase 2) 15 Dec December QA Team (Execution Group
started
2)

10 hours
Platform Not
PC QA Fixes (Phase 2) 20 Dec December (Execution Group
Consultant started
2)

4 hours
Client QA Fixes (Phase Not
10 Jan January QA Team (Execution Group
3) started
3)

1 hour
Development Not
Deployment (Phase 3) 15 Jan January (Execution Group
Team started
3)

Search Locator Development Not 8 hours (PC +


20 Jan January
Frontend Team started Dev work)

Search Locator Development Not 12 hours (PC +


30 Jan January
Backend Team started Dev work)

 Limited MS Hours: Burger Blocks has 40 hours this month (15 used, 25 remaining) and 20 hours
next month. All tasks must fit within these limits.
 No Additional Hours: The client will not purchase extra hours. All tasks, including the
enhancement and search locator updates, must be completed within the available hours.

 Design Approval: The design for the enhancement is already approved, focusing efforts on
development and deployment.

 Priority on Enhancement: The Yext Pages enhancement is the primary focus, with search locator
tasks being secondary.

 Estimated Time for Enhancement: The enhancement will take ~55 hours in total, requiring careful
prioritization of tasks.

 Search Locator Tasks: The search locator updates (front-end: 8 hours, back-end: 12 hours) must be
scheduled within the available hours.

 No Extra Costs: All work must be completed within the agreed hours with no additional cost to the
client.

 Client Feedback: The client will provide feedback at key stages (QA and fixes), allowing
adjustments within the allocated time.

 Execution Groups & Dependencies: Tasks are structured in execution groups to manage
dependencies and ensure timely completion.

Calculation by Month:

November 2024:
Template Set-Up, Teaser Card, General Styling: 14 hours (Complete)

Filtering, Active Filter Labels, Pagination: 10 hours (In Progress)

Total MS Hours for November:

14 hours (Template Set-Up, etc.)

10 hours (Filtering/Pagination)

Total Man-Hours for November = 14 + 10 = 24 hours

December 2024:

SEO, Analytics, and Developer Self QA: 11 hours (Not started, planned for December 5)

Visual QA: 5 hours (Planned for December 15)

Client QA Fixes: 4 hours (Planned for December 20)

Deployment: 1 hour (Planned for December 22)

Total MS Hours for December:

11 hours (SEO, Analytics)

5 hours (Visual QA)

4 hours (Client QA Fixes)

1 hour (Deployment)

Total Man-Hours for December = 11 + 5 + 4 + 1 = 21 hours

January 2025:

Search Locator Frontend Updates: 8 hours (Planned for January 15)

Search Locator Backend Configuration: 12 hours (Planned for January 30)

Total MS Hours for January:

8 hours (Frontend Updates)

12 hours (Backend Configuration)

Total Man-Hours for January = 8 + 12 = 20 hours

You might also like