Jason will be presenting the following sessions
Jason Yip - 8 guiding principles for Agile Coaches (or change agents) from the Spotify Ads R&D Agile Coaching teamJason YipStaff Agile CoachSpotify
schedule 1 year agoSold Out!
An introduction and explanation of 8 guiding principles design by the Agile Coaching team for Spotify Ads R&D and how they might help you with your own change efforts
- We are more impactful with both team-level insight AND leadership relationships;
- We should not become operational (or at least be careful about becoming operational);
- Focusing too much on short-term tactical wins limits the ability to have sustained impact;
- Coach (aka change agent) collaboration is more effective than silos;
- Results are for the short-term; systems and habits are for the long-term;
- Involving leaders (both formal and informal) in both brainstorming and implementation makes improvement faster;
- Coaching structure should follow coaching strategy; coaching strategy should follow product/business strategy;
- Sharing work and successes should be intentional, not just organic.
Jason Yip - Experimenting with BAPO in Spotify Ads R&D: aligning product strategy, technical architecture, ways of working, and org structureJason YipStaff Agile CoachSpotify
schedule 1 year agoSold Out!
BAPO stands for Business Architecture Process Organisation. It is Jan Bosch's more fleshed out expression of "structure should follow strategy". I recently experimented with applying this framework within Spotify Ads R&D and would like to share what worked and what didn't. Concepts expanded beyond BAPO to include product capabilities versus architecture services; overlapping product lifecycle s-curves; Simon Wardley's Pioneers, Settlers, Town Planners; and a reframing of the teaching people how to fish metaphor. Beyond sharing my successes and failures, this session will also encourage attendees to sketch how they might try this framework in their own context and anticipate what issues may appear.
1. What got you started/interested in modern software development methods?
Colleague sent me an article from XProgramming.com back in 1999.
2. What do you think is the biggest challenge faced by the software product engineering community today?
3. What do you think are the most exciting developments in software product engineering today?
The early majority finally catching up
4. Why did you choose the topic(s) you will be speaking about at the conference?
They are topical for me at the moment and hopefully this also means useful for the general audience. I assume every large organisation has issues with aligning structure to strategy and many attendees are change agents.
5. What are some of the key takeaways from your session(s) at Agile India?
Structure should follow strategy, but also technology and ways of working should follow strategy.
One of the most important principles for effective change is establishing and maintaining momentum.
6. Which sessions are you particularly looking forward to attending at Agile India this year?
Not sure yet... I'll probably hop around.
7. Any personal remarks/message you want to share with the software community?
Models are for the obedience of fools and for the guidance of the wise.