100 watermelon or a few words about the definition of success (Category Management)
A little earlier, I'm already. told scientific articleAssessing IT Project Success: Perception vs. Reality", which was devoted to the consideration of the changing understanding of the success of IT projects. Previously, this topic was actively pedaled by the guys from the Standish Group, even in the 1994 a year telling inThe CHAOS ReportThe fact that most IT projects fail. They considered success from the point of view of not just the project, but project management, or rather getting into the project triangle: timing, budget and scope in the form of all predetermined features.
The project is completed on time and on budget, with all features and functions as initially specified. I liked the new article, but the old one was originally a big bug in my head. I like to show this bug by example. 100 Measuring watermelon and assessing how much it takes pulp and how much crust:) Actually, the flesh is what is considered a success in the Chaos report, and the crust is what is considered a failure. Let's assume that in a conditional draft, as considered in the Chaos report 98 Features, as well as time and budget separately. It turns out that we have a hundred parameters in a multidimensional space and it would be funny just to imagine how much pulp there is in space. 100It is very difficult to imagine it, so let’s start with something simple.
- Imagine that we have a one-dimensional watermelon, and this is just a segment on the line and its center point on the left. And let's agree that the extreme ten percent of the segment on the right is a crust. Then the pulp will be 90% of our watermelon
- Now we move into two-dimensional space and here the watermelon will be a circle with a radius R, and far from the center. 10A crust occupies % of this radius. Amount of watermelon (in two-dimensional space, this is an area) Now it depends squarely on the radius, and it turns out that the pulp is everything. 0.9*0.9 = 81%
- In the usual three-dimensional space watermelon is a ball, the amount of watermelon. (Here's the volume.) Cubically depends on the radius and it turns out that the flesh 0.9*0.9*0.9 = 0.729 ~ 73%
- Continuing this reflection, we come to 100 watermelon, where the flesh will already be in homeopathic quantities, or rather 0.9^100 = 0.000027 ~ 0.0027%
- If we relax the requirements for each of the criteria in this one-dimensional space and make it so that we count any deviation less. 1% by any of the normal criteria, then we get much more flesh, or rather, 0.99^100 ~ 36,6% (That is, success will be in 36.6percentage)
Based on the results of these reflections on watermelons, it is clear that the initial definition of the success of the project from the Standish Group
The project is completed on time and on budget, with all features and functions as initially specified. It made little sense and only contributed to fueling fear about how poorly IT projects are managed. In a new study,Assessing IT Project Success: Perception vs. Reality"from this point of view, everything is done much better - the authors separate the assessment of success in this field." 7 They use the Lykert scale and ask about the global success of the project. This allows them to track individual correlations between global success and other criteria.
To sum up, I recommend reading the article to understand how the authors built their model of thinking and how it is applicable to your task:)
#Management #Math #Leadership #SystemDesign #CriticalThinking