Transparency is critical to the success of organizations and groups that embrace Agile. The Scrum events that help with transparency, including the Daily Standup, Sprint Planning, Sprint Review and Retrospective meetings. These all give the Developers and the Product Owner an opportunity to raise issues and be honest and open about things like team progress. The events also give the Scrum team the opportunity to adapt and improve. As far as I'm concerned, the Scope Governance Board is an extra event to achieve transparency.
Transparency in Agile cannot be overstated. In some organizations it is not easy to be transparent and open. There's a lot of pressure to say what the company wants to hear. But I believe that a lack of transparency damages an Agile team, the project, the organization and ultimately the company in the long run.
I've seen first-hand organizations that claim they want 'openness', but ultimately choose not to give that openness. Old beliefs that lead to fear and/or threat may still get in the way too much. Transparency is critical to the success of software development using Agile methodology and it is well worth it.
Lack of transparency can have a negative impact on many things, including on the cooperation between customer and supplier.
An important event that does not come from the Scrum Framework but I at my previous client INFO experienced was the Scope Governance. The assignment was to build a new product for one customer, in which I played the role of Scrum Master had.
How does it work and who is in it?
The Scope Governance Board met at the end of each sprint. It consisted of two representatives of the supplier and two representatives of the customer. In this case it looked like this:
Scrum Master (supplier)
Delivery Manager (supplier)
Product Owner (customer)
Program Manager (customer)
What topics do we discuss?
Benefits of working with a Scope Governance Board
My experience is that this meeting added a lot of value because participants share expectations among themselves. This contributes to transparency and trust. Why? We could immediately discuss and respond to every expectation that turned out differently. The representatives in these consultations were particularly aware of setbacks and disappointments in advance. Instead of having to expose your buttocks afterwards and irritations could already arise.
I hope I have inspired you to increase your transparency both within the team and beyond. And of course I am also curious, what are your success factors in increasing transparency?
Transparency is critical to the success of organizations and groups that embrace Agile. The Scrum events that help with transparency, including the Daily Standup, Sprint Planning, Sprint Review and Retrospective meetings. These all give the Developers and the Product Owner an opportunity to raise issues and be honest and open about things like team progress. The events also give the Scrum team the opportunity to adapt and improve. As far as I'm concerned, the Scope Governance Board is an extra event to achieve transparency.
Transparency in Agile cannot be overstated. In some organizations it is not easy to be transparent and open. There's a lot of pressure to say what the company wants to hear. But I believe that a lack of transparency damages an Agile team, the project, the organization and ultimately the company in the long run.
I've seen first-hand organizations that claim they want 'openness', but ultimately choose not to give that openness. Old beliefs that lead to fear and/or threat may still get in the way too much. Transparency is critical to the success of software development using Agile methodology and it is well worth it.
Lack of transparency can have a negative impact on many things, including on the cooperation between customer and supplier.
An important event that does not come from the Scrum Framework but I at my previous client INFO experienced was the Scope Governance. The assignment was to build a new product for one customer, in which I played the role of Scrum Master had.
How does it work and who is in it?
The Scope Governance Board met at the end of each sprint. It consisted of two representatives of the supplier and two representatives of the customer. In this case it looked like this:
Scrum Master (supplier)
Delivery Manager (supplier)
Product Owner (customer)
Program Manager (customer)
What topics do we discuss?
Benefits of working with a Scope Governance Board
My experience is that this meeting added a lot of value because participants share expectations among themselves. This contributes to transparency and trust. Why? We could immediately discuss and respond to every expectation that turned out differently. The representatives in these consultations were particularly aware of setbacks and disappointments in advance. Instead of having to expose your buttocks afterwards and irritations could already arise.
I hope I have inspired you to increase your transparency both within the team and beyond. And of course I am also curious, what are your success factors in increasing transparency?
It is our mission to help customers get their change ambitions to come true.
Our location in Amersfoort is located directly opposite the main entrance of the NS station and is therefore easily accessible by public transport.
If you come by car, it is best to park at the Q-Park P+R Barchman Wuytierslaan, approximately a 5-minute walk from our office.
