Session M7-02: Interview ideas and shape better work¶
Module: Product and Delivery Teams
Difficulty: Beginner
Prerequisites: Session M7-01 and working GitHub Copilot access
Duration: 3 hours (1 hour trainer content + 2 hours lab)
Overview¶
Continue the Delivery Decision Studio path with your Session M7-01 context brief. Install the supplied project skill and use it to ask questions in dependency order. Turn the approved answers into a decision brief and issue proposal. When a late constraint arrives, revise only the affected decisions.
The fictional Service Request Portal remains the initiative. Do not use customer requests or source organization names in the standard lab.
Important
GitHub Copilot is required. Check access before the session. If Copilot cannot run the interview, stop the lab.
Learning outcomes¶
By the end of this session, learners can:
- Install and check the supplied
decision-interviewproject skill. - Run a GitHub Copilot interview that asks only questions whose prerequisites are settled.
- Resolve scope, constraints, success, failure, ownership, and approval.
- Review Copilot recommendations before accepting or revising them.
- Create a reviewed Markdown decision brief in the repository.
- Draft an issue proposal with testable acceptance criteria and a practical definition of done.
- Reopen only the decisions affected by new source information.
- Check that the revised brief and issue proposal agree.
- Check context usage before each interview round and start fresh for the final review.
- Request an independent critique before approving the brief and proposal.
- Assign an owner and reviewer before work enters a sprint.
Session flow¶
Vague request
-> project skill installation
-> GitHub Copilot decision interview
-> human review and decisions
-> Markdown decision brief
-> GitHub issue proposal
-> acceptance criteria
-> definition of done
Session structure¶
| Block | Duration | Material |
|---|---|---|
| Trainer content | 1 hour | Trainer guide |
| Lab | 2 hours | Lab guide |
Materials¶
| Resource | Location |
|---|---|
| Marp slides | slides.md |
| Starter request and repository templates | lab/starter/ |
| Completed Copilot-reviewed examples | lab/solution/ |
Boundaries¶
- Teach the interview pattern, not skill authoring.
- Use only approved, sanitized material.
- Treat Copilot questions, recommendations, and drafts as proposals.
- Keep product and approval decisions with named people.
- Do not create or update a live work item until the request owner approves the brief.
- Keep the lab no-code. Learners install and use the supplied project skill; they do not author or edit it.
- Session M7-03 creates the approved GitHub issues. Session M7-02 prepares the source brief and issue proposal.