Magnus HedemarkandGitHub
22d141de75
* feat: add research-grounded technical project management skill * test: retain isolated project coordination regression evidence
2.2 KiB
Use one shared page and one small task board. Pick one engineer to maintain them for the next two weeks; rotate that role if useful. This is coordination work, not a new management layer.
Start with a single 30-minute conversation with the person who can approve the migration scope. Agree on the customer outcome, what is included and excluded, how you will know it worked, and who accepts it. Record the sales date as a requested date until you have a feasible plan and the approver accepts it.
Put these items on the shared page:
| Item | What to capture |
|---|---|
| Outcome and scope | One paragraph, explicit exclusions, acceptance checks |
| People and capacity | Each engineer's actual available days or hours per week |
| Milestones | Trial migration, readiness decision, cutover, customer acceptance |
| Dependencies and risks | Access, data quality, customer availability, blockers and owners |
| Decisions | Date, decision, reason, decision-maker, affected work |
Create board columns for Ready, Doing, Blocked, and Done. Each card needs one owner, a small deliverable, and a completion check. Start with discovery tasks wherever uncertainty prevents estimating; don't turn guesses into deadlines. Limit active work to fit your part-time capacity, and make dependencies visible before assigning target dates.
For the migration itself, include a trial run, reconciliation checks, backup and rollback, a named cutover decision-maker, and support after launch. Use these as readiness conditions rather than treating the requested date as permission to cut over.
Replace routine status meetings with a twice-weekly async note from each person: completed, next, blocked, capacity changes. Discuss only unresolved decisions, preferably in an existing meeting or a short ad hoc call. The coordinator updates the board and decision log immediately after agreements, so chat history is not your record.
By the end of the first week, aim for accepted scope, a visible backlog, realistic capacity, and a preliminary date forecast with assumptions. Ask the approver to choose scope or timing tradeoffs if that forecast misses the sales request. Revisit the lightweight process after two weeks and remove anything nobody uses.