4 ms·
This article makes a common mistake: Scrum and Agile are not synonymous. Given that error, the conclusion is nonsense. And besides, even Scrum doesn’t require a
by Jtsummers 7y ago
This article makes a common mistake: Scrum and Agile are not synonymous. Given that error, the conclusion is nonsense. And besides, even Scrum doesn’t require a delivered product each sprint. Just an updated status and increment completed.
If I’m building a new server and client architected system, the early sprints may be getting certain design details down. More documentation than code. Later on, I may have sprints that only establish the handshake between client and server and no real functionality. The point is taking milestones (big chunks of work) down to smaller chunks of work that can establish a clearer goal set for the near future.
And that isn’t even unique to Scrum. If you don’t establish small iterative goals it becomes difficult to measure progress. Saying, “We can’t measure success until this large number of lines of code are completed” is folly. If you have that design, you can measure your progress towards completion by creating inch-pebbles for the next few iterations. Like in my example, finalize design docs based on R&D efforts, make prototypes or simulations, create basic handshake code, then build up server and client features in tandem to ensure they make sense (maybe the design can be simplified when you realize several commands or messages are really specialized versions of a more generic one, or maybe something is more complex and requires a reexamination of the design). And yes, a lot of this is common sense to good engineers. Problem is, common sense isn’t common and you’ll get people pushing Waterfall again and again.
- iovrthoughtthis 7y agoAlso, if you can’t get a thing done in one sprint then perhaps your sprint is too short? The point is to adapt the process to the teams needs, not to dogmatically follow some other teams process.
- jogjayr 7y ago> This article makes a common mistake: Scrum and Agile are not synonymous It does not. It merely acknowledges that Scrum is the most popular and widely practiced incarnation of Agile and is what most developers are familiar with. From the article: "The simple high level Agile Manifesto is something I think is close to the way Google engineers think about software development...Google development style exemplifies the type of individual empowerment talked about in the principles." And: "While the high level Agile Manifesto is flexible enough to work with these principles, these are very different than the short-iteration low documentation Agile/Scrum process which has become synonymous with the word Agile."
- lanstin 7y agoWhen you are at the edge of technology a lot of the initial tasks are the smart people go off and think for a few weeks or months. Talking amongst themselves but not necessarily producing visible things. Just updating their mental state as they search solution space for the best achievable answer. Now, I have worked in a place where that time was accounted for and allowed, but most places the value of it seems lost on management.
- temac 7y agoIf you redefine "agile" as common sense and what currently works for you, and "waterfall" as failure, then obviously every good thing will be "agile", and wrong stuff will be "waterfall". Can we do anything with that though?