Module From-Scratch 30-Day Implementation Sprint

Platform target: ServiceNow Australia (Sep 2026) · next EA: Brazil
URLs: ../../SERVICENOW_DIRECT_URLS_CATALOG.html · 1-week: ../../SERVICENOW_ONE_WEEK_STUDY_DEPLOY_AUSTRALIA.html
HR Leave: Scope x_786686_hr_leave

التطبيق من الصفر — رحلة 30 يومًا

Universal 30-day playbook for any ServiceNow module. Customize the lane per module.

دليل تنفيذ 30 يومًا قابل للتطبيق على أي موديول. لكل موديول مسار خاص في ملف §18.

§1 — Purpose / الغرض

This is the master 30-day plan. Each module file (ITSM.md, CMDB.md, etc.) has its own §18 From-Scratch Implementation with module-specific day-by-day steps. This document standardizes the methodology, phases, gates, and templates.

هذا الملف يوحّد منهجية الـ 30 يومًا. أما تفاصيل كل موديول، فهي في §18 الخاص بكل ملف.

§2 — Sprint phases / مراحل التطبيق

┌─────────────┬─────────────┬──────────────┬──────────────┐
│ Foundation │ Build │ Integrate │ Launch │
│ (Days 0-7) │ (Days 8-18) │ (Days 19-24) │ (Days 25-30) │
└─────────────┴─────────────┴──────────────┴──────────────┘

§3 — Day 0 — Strategy & Charter

3.1 Charter document outline

Project: [Module Name] Implementation

Sponsor

[Executive name + title]

Business case

• Problem: [pain point]
• Outcome: [measurable target]
• Value: [dollars saved / risk reduced / time freed]

Scope (in)

• [bullet]

Scope (out)

• [bullet]

Success criteria

• [KPI 1 with target]
• [KPI 2 with target]

Timeline

• Kick-off: [date]
• Go-live: [date]
• Hypercare end: [date]

RACI

[table]

Risks

[top 5]

Budget

[licenses + services + internal hours]

3.2 Stakeholder map (RACI)

§4 — Days 0-7 — Foundation

4.1 Day 1 — Plugin activation template

Navigate: All > System Applications > All Available Applications
Search: <module>
Click: Activate (and dependencies)
Wait for completion
Refresh and verify navigation
Run: Guided Setup > <module>

4.2 Day 2 — Data model workshop facilitation

Ask:
1. What is the transaction record? (incident, case, asset, project)
2. What is the master record? (account, person, CI, profile)
3. What lookup records do you need? (categories, types, priorities)
4. What relationships matter? (parent-child, M:N)
5. What lifecycle states does each record have?

Output: 1-page ER diagram per table.

4.3 Day 3 — Role catalog template

4.4 Day 6 — Security model

§5 — Days 8-18 — Build

5.1 ATF coverage targets

5.2 Update Set discipline

• Naming: [YYYYMMDD]_
• Example: 20260601_HRSD_W1_HRCriteria
• Commit daily; never accumulate >100 changes per set
• Pre-commit review by tech lead

§6 — Days 19-24 — Integrate

6.1 Integration testing matrix

§7 — Days 25-30 — Launch

7.1 UAT scenario template

**Scenario ID**: UAT-<module>-01
**Title**: <title>
**Persona**: <Employee | Agent | Manager>
**Pre-conditions**: <state>
**Steps**:
 1. <action>
 2. <action>
**Expected**: <result>
**Actual**: <fill during test>
**Pass/Fail**:
**Defect ref**: <if any>
**Sign-off (BA + sponsor)**:

7.2 Cutover plan template

§8 — Days 30-60 — Stabilize (Hypercare)

8.1 Hypercare metrics

§9 — Per-module 30-day quick reference

Each module’s §18 has the day-by-day specifics. Quick reference:

§10 — Templates library

10.1 Daily standup script (Days 8-30)

1. Yesterday: what was completed
2. Today: what we’re working on
3. Blockers: what we need help with
4. Risks emerging: new or escalated
5. Metrics: progress % vs plan

10.2 Weekly status report (1-pager)

Week : Implementation

Status: 🟢 GREEN | 🟡 AMBER | 🔴 RED

Key accomplishments

• …

Upcoming next week

• …

Risks & issues

• …

Asks (sponsor / steering)

• …

KPIs (this week vs plan)

10.3 Defect triage template

**Defect ID**: D-<n>
**Severity**: P1 | P2 | P3 | P4
**Component**: <table | flow | widget | API>
**Description**:
**Repro steps**:
**Expected**:
**Actual**:
**Workaround**:
**Owner**:
**ETA fix**:
**Tested by**:
**Closed**:

§11 — Resource plan template (30-day sprint)

§12 — Risk catalog (typical 30-day project)

§13 — Go-live “rocket-launch” checklist (Day 28-29)

• [ ] Final smoke test passing
• [ ] Backup snapshot taken
• [ ] Code freeze in effect
• [ ] Comms sent (T-1 day)
• [ ] War-room booked (1st 72h post-launch)
• [ ] On-call rotation confirmed
• [ ] Support team briefed
• [ ] Rollback plan reviewed
• [ ] Monitoring dashboards open
• [ ] KPI baseline captured
• [ ] Day-1 sponsor message drafted
• [ ] Hypercare schedule shared
• [ ] Survey for Day-7 prepared

§14 — Common 30-day sprint outcomes

§15 — Post-30-day roadmap (Wave 2)

After successful Wave 1 (Days 0-30), plan Wave 2 (Days 31-90):

• Expand to more business units
• Add advanced features (AI, automation, advanced workflows)
• Integrate with more external systems
• Build cross-module experiences
• Maturity: from “running” to “optimized”

Use MODULE_ZERO_TO_HERO_CONSULTING.html Phase 8 (Run & Improve) for ongoing operations.