📣 BREAKING NEWS ‼️
avendo AG’s Post
More Relevant Posts
-
BREAKING NEWS !!!! BREAKING NEWS !!!! They tried to indoctrinated me!
To view or add a comment, sign in
-
The underlying joke here showcases a symptom when you focus too much on getting things (features) done quickly. I mean the problem is not the goal of having high throughput (ok, partially it is), it‘s the way how we think we can archive it. So the question shouldn’t be how can we set more feature’s done in the same amount of time (naive definition of productivity if you ignore quality in terms of rework and customer statisfaction). Instead you should ask how can we ensure that a feature is valuable? And I‘d like to start with three essential aspects of a valuable feature: * Full fills customer need * Defect free * Easy to change If you are able to find good principles and practices to ensure these three things you will likely maximaze the value output. Now I‘m questentiong myself, how can I measure these aspects to see if my work improves by adopting new princples and practices? Measuring quality on a (software development) process is something that I tried in my thesis years ago, and I used to design an individual GQM (Goal-Question-Metric) Model. But do you have any ideas or experience how to measure these?
Good News, Bad News
To view or add a comment, sign in
-
News you can lose
To view or add a comment, sign in
565 followers