Project management map
If you don't have a proper project manager, you could do worse than to fill in the blanks in this punchlist. It's useful to have resources lined up to solve these problems.
- Strategy, research
- Who do we think our customer is? What is their job-to-be-done?
- Strategy research
- Competitive analysis
- Lean business canvas
- User interviews
- Field research
- Market segments (for established product categories),
- Trend-spotting research (for fashion)
- Futures forecasting (pdf reports), , for startups.
- Kickoff, framing
- Exploration, scoping (pdf reports)
- Project brief (client services)
- Branding guidelines (if any preexisting brand)
- Customer stories, user stories, job stories
- Design Hypothesis
- Information architecture
- User testing
- Keynote interactive, etc
- Prototypes (test design hypothesis)
- More User Testing
- Loop back to Design Hypothesis
- Make as many loops as necessary, each one should resolve risks and move you closer to finding product-market fit.
- Interaction design, graphic design, motion design
- Asset sharing and versioning (Drive? GH? Something else?)
- Brand guidelines
- Copy guidelines/voice
- Brand colors
- Mobile or web or something else?
- UI framework/toolkit
- Build tooling
- Integration testing
- Automated (tool needed)
- Customer feedback in-app (tool needed)
- REST API
- Database structure
- CDN/asset server
- Real-time communication
- Unit tests
DevOps, Release engineering, release management
- Farm out as much devops as possible by using , AWS, etc
- Build scripts
- Nightly builds
- Continuous Integration
- Code peer review
- Someone else lands your code. Better yet, a bot. See the not rocket science rule
- Git branching strategy. or
- Automate everything: build bots, merge bots, CI bots
- Wikis are an excellent way to capture institutional knowledge, but require buy-in from a critical mass of the team. Making them a habit is key.
- is pretty good. is spam-prone.
- Markdown files in a GitHub repo can function as a pretty good documentation hub. Leverage the GitHub pull request workflow.
Building a Team
- Communication or , but be sure to implement team scrollback server for your channels.
- Automate as much grunt-work as possible with bots
Avoiding the morass:
Teams need special breaks with routine to stay sharp. Otherwise you get stuck wandering in the wilderness. Tools:
- Work week
- Google Hangouts