10. CAN TO HOW: ROLES
▸ YOU
▸ Bring expertise
▸ Make decisions
▸ Prioritize
▸ Determine business
model
▸ US
▸ Guide technology
▸ Explain tradeoffs
▸ Breakdown features
▸ Build software
11. HOW: STRATEGIES
▸ Identify Constraints
▸ Test and validate
▸ Fake it till you make it
▸ Build software around existing processes
18. CONFIDENCE STRATEGIES
▸ Identify goals that will drive value.
▸ Divide your project features in half. Do it again. Again.
▸ Earlier versions get earlier validation
▸ Welcome a change of course
21. WHAT’S WRONG WITH ‘TWEAK’
▸ Dismissive
▸ Sneaky
▸ No clear ownership / accountability
▸ Failure to make a decisions (indecisions in the group)
▸ Not data driven
24. USE A PROCESS
1. Identify problem
2. Clearly identify as ‘no decision’
3. Put it in the ‘icebox’ for explicit review later
4. Assign to someone to review
5. Identity how you get the data you need
6. Gather the data
7. Bring request into an iteration backlog for development
Bonus: Allow clear points of addition to project
28. SIGNAL STRATEGIES
▸ Consistent terms and processes
▸ Stand-up (specific ‘Needs’)
▸ Standard meeting agendas
▸ Define purpose of shared tool’s
▸ Slack vs Trello vs Email vs X
▸ Software Integrations
▸ Post to Slack
▸ Summarize
▸ Burn down chart
▸ Changelog, report
▸ Manage tasks
▸ Process and assign
▸ Roles
▸ Moments
▸ Delivery and demo