ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/devKalla-Fordonscervice/_wds/workflows/6-design-deliveries/steps/step-6.5-hand-off.md

5.9 KiB
Raw Blame History

Step 6.5: Hand Off to BMad

Your Task

Officially hand off the Design Delivery to BMad and confirm they have everything needed.

Before You Start

Ensure you have:

  • ✅ Completed step 6.4 (Handoff dialog complete)
  • ✅ Handoff log documented
  • ✅ Delivery status updated to "in_development"

Final Handoff Checklist

Verify BMad Has All Artifacts

Design Delivery:

  • File exists: deliveries/DD-XXX-name.yaml
  • Status: "in_development"
  • Handed off timestamp recorded
  • Assigned to BMad Architect

Test Scenario:

  • File exists: test-scenarios/TS-XXX-name.yaml
  • All tests defined
  • Sign-off criteria clear

Scenario Specifications:

  • All scenarios in C-Scenarios/ are complete
  • All specifications are up-to-date
  • All design references are valid

Design System:

  • All components in D-Design-System/ are defined
  • Design tokens are documented
  • Component specifications are complete

Handoff Log:

  • File exists: deliveries/DD-XXX-handoff-log.md
  • All key points documented
  • Epic breakdown recorded
  • Action items listed

Notify BMad

Send official handoff notification:

WDS UX Expert → BMad Architect

Subject: Design Delivery DD-XXX Ready for Implementation

Hi Architect!

Design Delivery DD-XXX ([Flow Name]) is officially handed off
and ready for implementation.

📦 Artifacts:
- Design Delivery: deliveries/DD-XXX-name.yaml
- Test Scenario: test-scenarios/TS-XXX-name.yaml
- Scenarios: C-Scenarios/ ([number] scenarios)
- Components: D-Design-System/ ([number] components)
- Handoff Log: deliveries/DD-XXX-handoff-log.md

✅ What we agreed:
- Epic breakdown: [number] epics
- Estimated effort: [time]
- Implementation approach: [summary]

📋 Next steps:
1. You: Create architecture document
2. You: Break down into dev stories
3. You: Implement features
4. You: Notify me when ready for validation (Touch Point 3)

🔗 Touch Point 3:
When implementation is complete, notify me and I'll run the
test scenarios to validate. We'll iterate until approved.

Questions? I'm available!

Thanks,
[Your name]
WDS UX Expert

BMad Acknowledges

BMad Architect responds:

BMad Architect → WDS UX Expert

Subject: Re: Design Delivery DD-XXX Ready for Implementation

Received! Starting work on DD-XXX.

📋 My plan:
1. Create architecture document (this week)
2. Break down into [number] dev stories
3. Implement over [time period]
4. Notify you when ready for validation

📦 Confirmed I have:
✅ Design Delivery (DD-XXX.yaml)
✅ Test Scenario (TS-XXX.yaml)
✅ All scenario specs
✅ All component specs
✅ Handoff log

I'll keep you updated on progress. Thanks for the thorough
handoff!

Winston
BMad Architect

Update Project Status

Update project tracking (if you have one):

# Project Status

## In Progress

### DD-XXX: [Flow Name]

- Status: In Development
- Assigned: BMad Architect
- Started: 2024-12-09
- Estimated completion: 2024-12-30
- Epics: [number]
- Designer: Available for questions

## Next Up

### DD-XXX+1: [Next Flow Name]

- Status: In Design
- Phase: 4-5 (UX Design & Design System)
- Designer: Working on scenarios
- Estimated handoff: 2024-12-16

Set Up Monitoring

Track progress:

Weekly check-ins:

  • Schedule brief sync with BMad Architect
  • Review progress
  • Answer questions
  • Unblock issues

Communication channel:

  • Slack/Teams channel: #dd-xxx-implementation
  • Quick questions welcome
  • Async updates appreciated

Milestone notifications:

  • Epic 1 complete → Notify designer
  • Epic 2 complete → Notify designer
  • All epics complete → Ready for validation (Touch Point 3)

Designer Availability

Make yourself available:

"I'm available for questions while you implement:

Quick questions:
- Slack/Teams: @designer
- Response time: < 2 hours

Design clarifications:
- Schedule 15-min call
- Review specifications together
- Update specs if needed

Blockers:
- Immediate response
- Unblock ASAP
- Adjust design if necessary

I want this to succeed!"

What Happens Next

BMad's Work (Phases 3-4)

Phase 3: Architecture

  • Create architecture document
  • Define technical approach
  • Identify dependencies
  • Plan implementation

Phase 4: Implementation

  • Break down into dev stories
  • Implement features
  • Write tests
  • Build the flow

Timeline: [Agreed time estimate]

Your Work (Phase 6.6)

While BMad builds this flow, you design the next one!

Return to Phase 4-5:

  • Design next complete testable flow
  • Create specifications
  • Define components
  • Prepare for next handoff

Parallel work = faster delivery!

Next Step

After confirming handoff:

[C] Continue to step-6.6-continue.md

Success Metrics

✅ All artifacts verified and complete ✅ BMad notified officially ✅ BMad acknowledged receipt ✅ Project status updated ✅ Monitoring set up ✅ Designer available for questions ✅ Clear next steps for both parties

Failure Modes

❌ Missing artifacts ❌ BMad doesn't acknowledge ❌ No monitoring set up ❌ Designer disappears after handoff ❌ No communication channel established ❌ Unclear next steps

Communication Tips

DO ✅

Be available:

  • Answer questions promptly
  • Unblock issues quickly
  • Provide clarifications

Be collaborative:

  • "How can I help?"
  • "Let's figure this out together"
  • "I'm here if you need me"

Be flexible:

  • Adjust design if technical constraints arise
  • Find creative solutions
  • Focus on user value, not ego

DON'T ❌

Don't disappear:

  • "I handed it off, not my problem anymore" ❌
  • Stay engaged throughout implementation

Don't be rigid:

  • "It must be exactly like this" ❌
  • Be open to technical suggestions

Don't ignore questions:

  • Respond within 24 hours
  • If you don't know, say so and find out

Remember: Handoff is not the end - it's the beginning of collaboration! Stay engaged!