Let’s stop guessing and start crowdsourcing data and information on this critical topic: Who is using what metrics under which context to what success? Participate in the agile metrics survey now.
Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers.
Food for Agile Thought’s issue #218—shared with 24,269 peers—delves into alignment and autonomy at an organizational level; we shed more light on something we all believe in understanding well — the waterfall process —, and we explore the necessary mindset to become a good coach.
We also learn more about an extension to the Lean UX canvas, handling the prioritization of hypotheses; we discover techniques to take agile UX research to the next level, and we applaud a new 2020 Product conference listing.
Lastly, we enjoy a BBC article on the man who brought you timeboxes. Well, sort of.
Did you miss last week’s Food for Agile Thought’s issue #217?
Are we still on the right track? Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns.
Update 2019-11-10: I re-edited text, added new graphics as well as an excerpt from the Scrum Guide to clarify the purpose of the Sprint Review.
Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers.
Food for Agile Thought’s issue #217—shared with 24,172 peers—delves into agile playbooks and the optimal Sprint length; we learn how to convince the finance folks to embrace ‘agile,’ and we figure out how team contracts and alignment maps support to create psychological safety.
We also appreciate the visualization of the path from waterfall to a product team that deserves the name; we get more clarity on product reviews when using dual-track agile, and we are surprised by the range of MVP costs.
Lastly, we enjoy a 5-minute video clip, reminding us of all the madness in our industry.
Did you miss last week’s Food for Agile Thought’s issue #216?
Welcome to the Agile Movers & Shakers interview series. Today’s guest is Viktor Cessan. Viktor has dedicated his career to helping companies consciously design organizations that keep motivation, engagement, and performance levels high. In the 14 years since he started working with Agile methodologies, he has helped companies such as Spotify, H&M, King, Avanza Bank, Telenor, and Sony Ericsson work more effectively.
Viktor has coached teams of as few as 5 members to organizations with more than 200 people, enabling them to greatly improve their effectiveness as well as levels of happiness and well-being. He specializes in working with executive teams to help implement company-wide agile transformation.
Viktor runs training and workshops on a wide variety of topics such as agile team dynamics, product ownership, leadership, and management. His case study detailing his work with Avanza’s agile transformation has been downloaded and shared thousands of times.
Viktor holds a diploma in professional coaching (ICF), is a Certified Scrum Professional (CSP), Certified Scrum Master (CSM), and Certified Scrum Product Owner (CSPO). And in addition, he has extensive experience in/with FIRO, SCARF, Virginia Satir’s work, and Tuckman’s and IMGD.
Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers.
Food for Agile Thought’s issue #216—shared with 24,073 peers—delves into the product-market fit concept with statistics, frameworks, and models; we discover the essential elements of high performing teams, and we kiss fixed-everything contracts good-bye.
We also learn from Spotify how to speed up user research by not focusing on running more user interviews, and we look behind the scenes of WeChat and its — by Western standards — unconventional approach to innovation.
Lastly, we enjoy the unpacking of “iteration” and question the language of our community.
Did you miss last week’s Food for Agile Thought’s issue #215?
