A Discovery Project from Kickoff to Handover
On this page
In this lesson, you will learn:
- The phases of a Discovery project
- What a sign-off gate is and why it matters
- The 12-week plan for Project Clear View
🔁 Quick look back: Last time: Why Companies Buy Discovery. You learned the five business reasons for Discovery, and a measure for each.
1 The Problem: Nobody Knows What Happens When
The SOW says 12 weeks. But SNWR’s team has never seen a Discovery project. At your first call, you hear:
- Priya asks when she must build the MID Server hosts.
- Farah asks when the first scan will run.
- Anita asks when she has to sign anything.
👉 The fix: Show the whole project on one page: the phases, the weeks and the sign-off gates.
2 The phases of a Discovery project
Most Discovery projects follow the same path. The names change, but the order doesn’t.
| Phase | What happens |
|---|---|
| Prepare | Read the SOW, check the instance, find the people. |
| Understand | Workshops, questions, requirements and CMDB checks. |
| Design | Decide how Discovery will work at this client. |
| Prerequisites | Get hosts, firewall rules and accounts in place. |
| Build and pilot | Configure Discovery, scan one device, then a small range. |
| Test | Prove the data meets what was agreed. |
| Roll out and hand over | Go live in waves, then train the client’s team. |
💡 Good to know: Need a refresher? See ITSM Implementation › Implementation Methodology › Implementation Phases, from Kickoff to Hypercare for the general method.
3 Sign-off gates
A gate is a point where the client signs that a phase is done. You don’t move on until it’s signed.
- Gates stop the project from building on guesses.
- They give Anita clear moments to say yes or no.
- They protect you. A signed gate can’t be quietly reopened.
⚠️ Heads up: The prerequisites phase often takes longer than the build. Start requests early, even before design is signed.
4 Project Clear View: How We Implemented It
📍 Situation: SNWR’s team wants to know when they’re needed. Kickoff is in a few days.
🧭 Decision: Build a one-page, 12-week plan with six gates, and show who is needed in each week.
🛠️ Steps we took:
- Split the 12 weeks into phases, from week 0 (prepare) to weeks 11-12 (hypercare and handover).
- Placed the six gates: requirements (week 2), design (week 3), prerequisites (week 5), pilot (week 6), UAT (week 9), handover (week 12).
- Started prerequisite requests in week 2, so hosts and firewall rules are ready by week 5.
- Added the SNWR people each week needs, such as Priya in weeks 2-5.
✅ What we verified:
- Priya, Ravi and Farah can see exactly when they’re needed.
- Anita knows the six dates she’ll be asked to sign.
📁 Evidence: The Clear View 12-week plan, shared at kickoff (see Kickoff Call › The Project Plan and Timeline).
5 Quick recap
- A Discovery project runs: prepare, understand, design, prerequisites, build and pilot, test, roll out and hand over.
- A gate is a point where the client signs that a phase is done.
- Clear View has six gates over 12 weeks.
- Start prerequisite requests early. They’re often the slowest part.
6 Check yourself
Think of your answer first. Then tap to check.
1 What is a sign-off gate? Show answer
A point where the client signs that a phase is done, before the project moves on.
2 Why did Clear View start prerequisite requests in week 2? Show answer
Hosts, firewall rules and accounts take weeks at most clients. Starting early keeps week 5 on plan.
3 Who signs the gates on Clear View? Show answer
Anita Rao, the sponsor, with Hana’s input.
Nice work! You can see the whole Discovery project on one page. 🎉
Next up: Meet the Client: SNWR and Project Clear View
Was this lesson helpful?
Please log in to share lesson feedback.
Have a question or doubt?
Ask here and get help from instructors and fellow learners.
Only logged-in learners can post.
