Rosanna Sibora@airwhale @nobsagile challenge accepted ;) tactics on change?
My no. 1: co-creation.
Clear ownership is the best way to make change happen, and the best way to achieve ownership is to co-create the future.
Your thoughts?
TormodI strongly agree with this one, co-creation really increases the buy-in and strengthens the understanding between business teams and technical teams.
Another aspect of co-creation is the vital importance of fast feedback. So much time is lost when we are waiting for a response to a minor clarification or decision. Here we fall back to the principle that “Business people and developers must work together daily throughout the project.” (So often, we don’t in reality.)
This really accelerates a shared understanding and alignment on what we are building which increases the quality of what we deliver.
Thomas@airwhale @RosannaSibora I agree IF co-creation works! I too often see a kind of "handover" and the expectation that three textlines are enough to finish a story. "No time" to work more on it. That is a bad sign for the Work-Feedback Loop!
Yes, a classic problem. ”Hand-over”should be replaced by ”end of User Story with acceptance criteria met”.
Sure, business may spend a little more time during the sprint, but zero time in rework and have value delivery from day one.
@airwhale @RosannaSibora Exactly - and that does work great - had that experience in some situations.
@nobsagile @airwhale Co-creation works when people make it work. It needs proper facilitation, commitment, rules…
Are we talking about co-creation within big change initiatives or within an agile product team?
Multiple agile product teams within large corporations mainly.
Anecdotally, I find that organisations that make it work have a healthy representation of women in both operational and management positions.