Re: [scrumdevelopment] Failed and Challenged Projects (Re: Agile Method Research Study)
- 2013/7/24 woynam <woyna@...>
Oh, please. Our start and end dates are not fictional. When we start pre-planning, i.e. building the feature backlog from the approved project charter, the project officially starts.
When the (final) changes are rolled into production, the project ends.
Any followup work (e.g. enhancements, bug fixes) is performed as a separate project.well this is one of the things that for me agile is changingI prefer projects that put stuff in production asap, I have lead projects that in sprint 1 (aka after one week) we put stuff in productionin your defintion we would have a new project every weekfor me a project then ends when we stop enhancingin some case this even means when the software is no longer usedand when you use that definition there is no end date, and no slipping of end datewe put new stuff in production every sprint (ok mostly)
I agree that one can not set a realistic end date upfront, and sometimes the start date may be a work of fiction based on team availability. End dates slip, no big surprise. But once the project is done, it's done.
--- In email@example.com, Laurent Bossavit <lolists@...> wrote:
>> Hi Mark,
> > I don't quite understand why you think projects don't have duration.
> Because a "project" is a social construct, like a new fashion. Looking back after its time, you can always *tell* when it started and ended (more or less, some things live on pretty much forever, like ties).
> But at the time it starts, there is no intrinsic truth as to whether a given fashion "really" is a 6-month thing or a 6-year thing. It's not determined by the "thing" that a fashion is, because there is no "thing", only a dynamic pattern of social interactions.
> > For accounting purposes, we have to track the start and end dates of the projects. Of course, the end date may keep moving, but eventually the project is closed, even if it's canceled.
> Yes, I understand that part of the social construct is that we negotiate fictional start and end dates. Fiction can be pretty definite - it is a fact (in the sense of a statement accepted as canonical) that Sherlock Holmes retired in 1904 (give or take a bit) - even though he never actually existed. (And his retirement date was certainly not an attribute of Sherlock Holmes in any real sense when Doyle started writing his adventures.)
> Projects are convenient fictions, of which "facts" are determined in retrospect. The Cone, in implying that there is a "real" project with a "real" duration determined at the start, conveys a falsehood.
- That's exactly the point. Here, we are defining the end as the ACTUAL end when you stop charging your time. When you think you're going to be done in 2 weeks (the estimate) but you don't finish for 2 months (the actual end), you obviously have some amount of uncertainty in your estimate even if you don't realize it. That uncertainty is supposed to be reflected in the cone, but in practice, that cone doesn't taper; it is hangs around your estimates like a thundercloud until you stop charging your time to it.On Tue, Jul 23, 2013 at 10:58 AM, Yves Hanoulle <mailing@...> wrote:
2013/7/22 Cass Dalton <cassdalton73@...>The high level concept that the cone portrays (estimation uncertainty is IN GENERAL higher the the farther away you are from the end) is true.well you have to keep in mind that there is a BIG difference between being close to the end and thinking you are close to the end.However, the shape of the cone is based completely on someone's subjective theory, not on objective, empirical data. That is the only real point that Laurent is trying to make. He backs the argument up with intuition that 1) estimates in software development usually tend toward UNDER estimation, not OVER estimation, so the cone is not symmetrical as the original plot suggests, and that 2) the smooth tapering in the curve often doesn't happen as the last 90% of the work takes the last 40-50% of the time.Based on my experience in a traditional environment, I would say that the cone is rarely correct as presented in the plot. Estimates are low at least 85% of the time, and the uncertainty often doesn't taper anything like how the plot suggests. The times when estimates are high come from people who have been bitten by the always low estimates enough that the add in so much padding that their estimates are always unrealistically high. And then you have the rule that the work will tend to fill the estimate, completely skewing any empirical evidence you think you have. (The empirical evidence or lack thereof being the entire crux of Laurent's argument).On Mon, Jul 22, 2013 at 1:20 PM, George Dinwiddie <lists@...> wrote:
Mark,You can read some of what Laurent says about it at
On 7/22/13 12:46 PM, woynam wrote:
> Sorry, but I'm not buying the plug. If it's wrong, please tell us why.
https://plus.google.com/115091715679003832601/posts/FKLauKLZECmLaurent questions that
> I agree that it's probably not "scientific". As we've been
> discussing, getting real numbers is tough in the SW field.
> Based on my experience, I'd say the cone is very close to correct,
> given a fixed-sized starting backlog, which is almost a certainty in
> a traditional contract-upfront project.
- the cone is presented a symetrical, with as much room for
underestimating as overestimating, even though it's impossible to
complete a project in negative time
- that the cone seems to say that we necessarily get tighter estimates
when we approach the end, though in reality some projects stay at "90%
done" for a long time
- that the cone is taken for empirical data, but is based on Boehm's
> My most recent "large" project, a legacy mainframe migration project,
> was 2.5 years long, and the final costs were 2.5 times higher than
> our initial estimates. Of course, as we peeled away the layers of the
> legacy system, there was more junk in there than even the biggest
> pessimists imagined. You can see our burn-up chart in the 'Files'
> section of this group (Burnup Chart Example.jpg).
> --- In firstname.lastname@example.org, Yves Hanoulle <mailing@...> wrote:
>> 2013/7/22 woynam <woyna@...>
>>> The figures from Standish need to be taken with a *huge* piece of salt.
>>> A project is considered a "failure" or "challenged" based on its ability
>>> to come it at, or under budget. We all know in the agile community that the
>>> initial budget estimate is the *worst* possible estimate, given that its
>>> derived with the *least* amount of information.
>> I assume that statement is based on the cone of uncertainty.
>> I encourage you to read Laurent Bossavit's book
>> You will learn that the cone is not scientific at all (yes I agree it feels
>> right, well it's not correct..) I won't disclose at what level it is wrong,
>> let me just say it feels counter intuïtive. (mm isn't agile about doing
>> some counter intuïtive things ;-) )
>>> Lately, I've made sure that I refer to projects as being "under budgeted",
>>> rather than "over budget".
>>> I'd like to see a report that critically reviews projects to determine if
>>> the actual money spent was inline with the knowledge gained during the
>>> project. In other words, if you discover something on day 100 that you
>>> didn't know on day 1, would you have changed your estimate on day 1 if you
>>> knew what you didn't know. I'm guessing these percentages would flip-flop.
>>> --- In email@example.com, Diana Young <diana.young@>
>>>> That being said, the reality is that globally a lot of money is spent
>>> each year on software development projects and the results are less than
>>> stellar. The Standish Reports estimate that approximately 25% of all
>>> software development project are considered failures, about 30% are
>>> considered successful, and the remainder are challenged in some way
Want to speak at AgileDC October 8, 2013? http://agiledc.org/speak/
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org