Skip to main content
added 7 characters in body
Source Link

Welcome to the absolute average Scrum/agile project.

Scrum is a super fragile construct that fails as soon as one of the key actors (company lead, product owner, scrum master, team) does not understand (or does not want to follow) their role.

One thing that amplifies that problem is that Scrum means to take power from the managers and give it to the developers. And, guess what, most people in power don't like to give that power to others.

That's how we ended up where we are now: companies transform to agile, because having that word in your company's description is en vogue, companies transform to agile in name only.

So in the end, you have three options:

Beat them

Beat them Get Get management, the team, the other teams and everyone else to move to proper scrum. Good luck with that.

Join them

Join them Improve Improve what you can (e.g. remove the second daily and daily velocity reporting) and game the system for the rest. For example count training/testing/code reviews towards the velocity and overestimate tasks to include all of the above. You get what you measure, so include what you want in the measurement.

Leave them

Leave them If If you can't work with that system, get another job with a better system.

Welcome to the absolute average Scrum/agile project.

Scrum is a super fragile construct that fails as soon as one of the key actors (company lead, product owner, scrum master, team) does not understand (or does not want to follow) their role.

One thing that amplifies that problem is that Scrum means to take power from the managers and give it to the developers. And, guess what, most people in power don't like to give that power to others.

That's how we ended up where we are now: companies transform to agile, because having that word in your company's description is en vogue, companies transform to agile in name only.

So in the end, you have three options:

Beat them Get management, the team, the other teams and everyone else to move to proper scrum. Good luck with that.

Join them Improve what you can (e.g. remove the second daily and daily velocity reporting) and game the system for the rest. For example count training/testing/code reviews towards the velocity and overestimate tasks to include all of the above. You get what you measure, so include what you want in the measurement.

Leave them If you can't work with that system, get another job with a better system.

Welcome to the absolute average Scrum/agile project.

Scrum is a super fragile construct that fails as soon as one of the key actors (company lead, product owner, scrum master, team) does not understand (or does not want to follow) their role.

One thing that amplifies that problem is that Scrum means to take power from the managers and give it to the developers. And, guess what, most people in power don't like to give that power to others.

That's how we ended up where we are now: companies transform to agile, because having that word in your company's description is en vogue, companies transform to agile in name only.

So in the end, you have three options:

Beat them

Get management, the team, the other teams and everyone else to move to proper scrum. Good luck with that.

Join them

Improve what you can (e.g. remove the second daily and daily velocity reporting) and game the system for the rest. For example count training/testing/code reviews towards the velocity and overestimate tasks to include all of the above. You get what you measure, so include what you want in the measurement.

Leave them

If you can't work with that system, get another job with a better system.

Source Link

Welcome to the absolute average Scrum/agile project.

Scrum is a super fragile construct that fails as soon as one of the key actors (company lead, product owner, scrum master, team) does not understand (or does not want to follow) their role.

One thing that amplifies that problem is that Scrum means to take power from the managers and give it to the developers. And, guess what, most people in power don't like to give that power to others.

That's how we ended up where we are now: companies transform to agile, because having that word in your company's description is en vogue, companies transform to agile in name only.

So in the end, you have three options:

Beat them Get management, the team, the other teams and everyone else to move to proper scrum. Good luck with that.

Join them Improve what you can (e.g. remove the second daily and daily velocity reporting) and game the system for the rest. For example count training/testing/code reviews towards the velocity and overestimate tasks to include all of the above. You get what you measure, so include what you want in the measurement.

Leave them If you can't work with that system, get another job with a better system.