Toujours positif Toujours confiant Toujours souriant. Grand et unique ciro. Toujours il va reste dans mon cœur et dans mes souvenirs inoubliable que le dieu te protège ivica todorov
As much as I like the two and find their work valuable, it seems to me that they have not really understood Agile, especially SCRUM. For example : if a product owner is micro-managing ( as mentioned in the video ), then this is an agile antipattern. Instead his purpose is to help the team to build the right thing. Whereas the team is responsible to build the thing right. This belief war of Lean vs Agile is not helpful ( in my point of view Agile just extends Lean with customer involvement, risen from the need of more and more customization of the end product ). "Scrum derives from lean manufacturing invented in Japan." ( Jeff Sutherland )
Couldn't agree with you more!.. Much as I love her and her husband's work, at last I find something with which I vehemently disagree!.. In the 2nd half of the video, they just don't know what they're talking about! "A Product Owner [is a dictator who] makes all the decisions"? "A User Story / Product Backlog is a list of requirements"? "Amateur design"? .. "2 weeks is too slow"? You can see the interviewer gently trying to challenge them by asking a couple of questions, but you can see from the body language (direction of their eyes) that they aren't listening to him, they're just listening to each other and Mary's preconceived ideas.
For the curious mind, this is the paper mentioning “good estimates are 25% off, 75% of the time”: “Software Engineering Metrics and Models” books.google.com/books/about/Software_engineering_metrics_and_models.html?id=PKlQAAAAMAAJ
Vasco - this is a great example of the value of moving the focus from local optima (story estimates) to global optima (# of stories in the project). Now I have to figure out what new lessons there may be here for product development outside of software.
I like an answer to a question from the audience. Use an Agile Coach who can code to the specific context. First an admission that one cannot have all the answers. Second, there is value in a Agile Coach with contact with the code, although there does seem to be some kick back against this. This is my take on "Go and see". Thirdly, the fact you cannot code because your busy attending to other items is an indicator that there are still symptoms from undiscovered/untackled root causes.
The average is 1/2 the answer, the variance of that average is critical to the forecast. Read Flaw of Averages before spending other people money with the approach goo.gl/38SJxh This still doesn't answer the "business" question of capabilities delivered in the fixed cost and schedule paradigm. Huge assumptions about the consistency of the Story size. The word "proof" "no" and "always" tossed around with cavalier abandon
The average is not the only answer, but it is part of the answer. And BTW it delivers - in some cases - much more accurate predictions than expert estimations. But you should watch the whole video, not just the parts about averages :)
w/o knowing the variances and the source of the variances, making decisions using the average is sporty. I watched the whole video. When there is less confidence in the math, it weakens the argument.
The point is to derive actionable heuristics for day to day decision making. I have found those. The math will evolve to accommodate empirical evidence. It ALWAYS does
that's great, but the "all in cost" at time of funding - beyond your fixed cost fixed time" paradigm is not provided by this approach. It all comes down to the domain applicability issue
Domain hopping is something that always happens with ideas like these. I know this one will also hop into your domain. The question is who will be rich and famous for doing so ;)
