This document discusses project management growth practices and contains recommendations in several areas:
1) Be available to your team to reduce dependencies, optimize around available resources which may be constrained by project management, engineering or the team itself.
2) Improve processes by setting up project management software, using demos to drive progress, and dedicating special days to areas like bugs, polish or internal tools.
3) Anticipate risks and have mitigation plans to determine if risks are real problems, and have rollout or other plans to address risks like stability issues.
4. OPTIMIZE AROUND YOUR TEAM'S RESOURCES
• Design constrained
• PM constrained
• Engineering constrained
5. IMPROVE YOUR TEAM'S PROCESSES
• Set up project management software
• Use demos as a forcing function
• Use special days to invest in areas that get overlooked
9. Use special days to invest in areas that get overlooked
• Bugs
• Polish
• Internal Tools
10. SNIFF OUT RISKS AND MITIGATE THEM
For each risk, come up with a mitigation:
• Can you do something now to determine if the risk is a problem? Perhaps you can run a
concept or usability test now.
• Can you set up a plan to handle the risk? For example, if stability is a risk, you should
probably plan for a slow rollout in order to catch problems while they're small.
• Can you set up a plan to handle the risk? For example, if stability is a risk, you should
probably plan for a slow rollout in order to catch problems while they're small.
11. DRIVE QUALITY AND VELOCITY IMPROVEMENTS ACROSS
PRODUCT TEAMS
• Launches hit their dates but miss their targets
• Launches miss their dates
• Teams spend a lot of time on other priorities instead of their main project
• Process slows the team down
• Mismatch between your expectations and the skill level of the teams