Workflow

Project Management

Engineering management

Get things started

• list of project stakeholders
• kick off with the team - express the why
• Setup one place for documentation, feature readiness checklist and one place for files
• Setup a Project board, a chat group, email group
• Inventory of knowledge: list tech and team familiarity

Day to day

Seek velocity early, from week 1 or 2

• Organise the frequent sync (like standup meetings)
• Demo work progress
• Call out/evaluate risks as you spot them
• Have a status page
• Update weekly project stakeholders

Notes

• Delegate up and down. Someone in charge of running standups/prepping demos/managing Jira
• Have clear milestones, crystal clear next steps

Standup

• Have everyday a bell to get it started. Track time.
• As people raise obstacles, take note on improvement board

Productivity

What to work on

1. Offload from the brain everything that needs to be done
2. Every morning assess them against them against the Eisenhower Matrix

3. If items are left to prioritize, use the ICE principe

1. The positive Impact it would have if it succeeds.
2. The confidence you have that it will succeed if you try it.
3. How easy it would be to try it.

-> Mental models by Julian

Communication

A good roadmap

The litmus test for a good product roadmap is that it’s visual, accessible and clear enough for anyone to scan for answers to the following questions:

• What are we doing?
• Why are we doing it?
• How does this tie back to our OKRs?

Tips

• Communicate problems to be solved and open up the conversation around how to solve them.

• Leave room to adjust to change

References

• How To Build A Product Roadmap Everyone Understands
• Productivity Isn’t About Time Management. It’s About Attention Management
• Tech Lead Expectations for Engineering Projects (Gergely Orosz @Uber)
• It's not just standing up