Check these out next
Real Cross-functional Teams for Creating real and better Products
1 gostaram
visualizações
At the core of agile development are self-organizing cross-functional teams. Yet, this is often understood as e.g., backend & front-end developers working together. If an organization is aiming for company-wide agility, to fully benefit from agility it has to enable teams as value centers that are truly cross-functional by bringing in different perspectives from business, markets, cultures, beliefs etc. This way cross-functional teams overcome not only the limitations of organizational silos but also of a singular view on the market. Too many products have been developed that serve one kind of client only. The reason is that the composition of the teams leads (subconsciously) to the development of products that serve only people that resemble the people in the team. One “famous” example is the soap dispenser that only works if your hands are white. If teams are really cross-functional and are resembling the diversity of the market, the products they’re creating are also better. Thus, if the whole team has the full business expertise, knows the market, reflects the full diversity of the clients, then it can even disrupt the market and isn’t waiting for some person (e.g., the Product Owner) to decide on priorities. With this real cross-functionality the team can fully understand the company’s business and has a holistic view of it, knowing its contribution to the company’s value stream. Real cross-functional teams are an essential building block for implementing company-wide agility and the organization benefits by creating better and in a way more real products and by having more options when entering the war of talent.
Recomendados
Real Cross-functional Teams for Creating real and better Products
- @leanarchitect | @JuttaEckstein 1 1 Jutta Eckstein | @JuttaEckstein www.JEckstein.com Maryse Meinen | @leanarchitect www.agileforlife.org Real Cross-functional Teams for Creating Real and Better Products
- @leanarchitect | @JuttaEckstein 2
- @leanarchitect | @JuttaEckstein 3 Can the product team on the left build for the user population on the right? © https://guidestudio.com/ideas/developing-a-brand-for-diverse-audiences/
- @leanarchitect | @JuttaEckstein 4 Inclusive Products? ■ There are five required tests to approve a car for the EU ■ In no test is a female crash-test dummy required
- @leanarchitect | @JuttaEckstein 5 Inclusive Products? ■ Map apps that fail to account for women’s desire for ‘safest’ in addition to ‘fastest’ routes ■ Virtual reality headsets that are too big for the average woman’s head ■ Microphones that require either a waistband or substantial pockets to attach to
- @leanarchitect | @JuttaEckstein 6
- @leanarchitect | @JuttaEckstein 7
- @leanarchitect | @JuttaEckstein 8 An organization produces a design that reflects the organization's biases. Eckstein’s Law
- @leanarchitect | @JuttaEckstein 9 Differences & Exchanges Source: https://www.hsdinstitute.org/resources/difference-matrix.html high low Exchanges Differences low high
- @leanarchitect | @JuttaEckstein 10 Changing Differences & Exchanges high low Exchanges Differences Emerging ◼ Decrease exchanges: • Reflection • Separation • Rest Uncoupling ◼ Decrease differences: • Identifying similarities • Creating common group stories Reinforcing ◼ Increase differences: • Identifying differences • Asking for opinions Belonging ◼ Increase exchanges: • Using questions and stories low high Source: https://www.hsdinstitute.org/resources/difference-matrix.html
- @leanarchitect | @JuttaEckstein 11 Chat Storm ■ What are your recommendations for cross-functional teams?
- @leanarchitect | @JuttaEckstein 12 Our Recommendations for Cross-functional Teams ■ Ask for different perspectives within the team ■ Ask for anonymous feedback ■ Consent decision-making ■ Explicitly use inclusive techniques to hear all voices
- @leanarchitect | @JuttaEckstein 13 Consider (a Spectrum of) Personas Source: ©David Dame, Microsoft, https://bit.ly/3EYNdXk
- @leanarchitect | @JuttaEckstein 14 Inclusive Language ■ Personal characteristics only when relevant ■ Careful with meritocracy language ■ Gender inclusive practices ■ No expressions or metaphors
- @leanarchitect | @JuttaEckstein 15 Thank you! Jutta Eckstein, @JuttaEckstein Jutta@JEckstein.com http://JEckstein.com Maryse Meinen, @leanarchitect marysemeinen@xs4all.nl www.agileforlife.org