Agile
Follow agile principles over following exact steps of some predetermined safety dance.
Scrum as patterns
Scrum as a team patterns for problems & solutions is a good way to think about agile. The scrum patterns have a recommended order of implementation. It starts from stable teams
- Stable team
- Product owner to lead the vision and developmnet team that can focus on building
- Someone to lead the develppment team's learning and adherence to agreed principles.
- Backlog of stuff to do that delivers value
- Daily adjustments to work plan
- Review after some agreed cadence
- Shipping in regular increments
- Regular reflection and opportunity for introspection
Source [1]
Notes
- Think big, act small
- Team boundaries
- Running a discovery phase as a sign of change
- Agile won't get you to done
- Jira
Quotes
Integrate principles, not processes
#mtpcon speaker says "I hate Agile. It's all points and velocity. No one talks about the customer." 1,400 people applaud. #AgileBrandProblem pic.twitter.com/pHEOFtCuA6
— Jeff Patton (@jeffpatton) September 30, 2016
Lean vs Agile vs Design Thinking
Disciplines
Notes:
- Principle #1 Customer value == Business Value
- Principle #2 Work in short cycles
- Principle #3 Hold regular retrospectives
- Principle #4 Go and see
- Principle #5 Test high risk hypothesis
- Principle #6 Do less more often
- Principle #7 Work as a balanced team - small, dedicated, (co-located), cross-functional, autonomous, empowered. No developer, delivery team and discovery teams.
- Principle #8 Radical transparency
- Tactic: Transparency through rituals
- Tactic: Access to data
- Tactic: Access to customers
- Principle #9 Review incentive structures
- Principle #10 Make learning a 1st class citizen of the backlog
Resources
Articles
- How to get executive buy in for agile using two popular product development approaches
- Dear PMs, It's Time to Rethink Agile at Enterprise Startups
See Shturmovshchina and Udarnik