Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
When Scrum becomes the very evil it was to overcome
|
There’s no doubt that Scrum has becomeThere’s no doubt that Scrum has become the most popular of Agile methods for software development and other projects, but if we step back a moment, we have to sometimes realize that it is a lightweight “framework” for managing projects, whereas Agile as outlined in the Agile Manifesto is a set of “values”.
There’s no doubt that Scrum has become the most popular of Agile methods for software development and other projects, but if we step back a moment, we have to sometimes realize that it is only a lightweight “framework” for managing projects, whereas Agile as outlined in the Agile Manifesto is a set of “values”. It is your responsibility to align the use of Scrum with the Agile values.
With this being the case, I’m getting lots of anecdotal evidence that Scrum is becoming within the industry the very evil it was to overcome. Namely, a rigid command and control process that enforces a mechanistic adherence to iterations, ceremonies and artifacts. Examples would be a rigid conformance of spring planning models that must follow specific ceremonies, maintaining who controls and manages the backlog, and how Sprints should be deployed (or rudely “pushed” out).
This rigid robot like mindset is quite antithetical to the values and sprit of Agile, but with the commercial success of a method like Scrum and it’s widespread adoption both within its software development roots and outside it, there seems to be a growing trend of a more dogmatic, stifling and stale version of Scrum that is permeating the industry.
Like I mentioned, I don’t have lots of data either quantitative or qualitative to back this up, but it is a sentiment that seems to be growing and shared amongst those who for the most part feel that Scrum was pushed down on them because someone heard it was a popular Agile method.
Am I right or wrong? I’d like to know what you think!
Am I right or wrong? I’d like to know what you think! the most popular of Agile methods for software development and other projects, but if we step back a moment, we have to sometimes realize that it is a lightweight “framework” for managing projects, whereas Agile as outlined in the Agile Manifesto is a set of “values”.
With this being the case, I’m getting lots of anecdotal evidence that Scrum is becoming within the industry the very evil it was to overcome. Namely, a rigid command and control process that enforces a mechanistic adherence to iterations, ceremonies and artifacts. Examples would be a rigid conformance of spring planning models that must follow specific ceremonies, maintaining who controls and manages the backlog, and how Sprints should be deployed (or rudely “pushed” out).
This rigid robot like mindset is quite antithetical to the values and sprit of Agile, but with the commercial success of a method like Scrum and it’s widespread adoption both within its software development roots and outside it, there seems to be a growing trend of a more dogmatic, stifling and stale Scrum that is permeating the industry.
Like I mentioned, I don’t have lots of data either quantitative or qualitative to back this up, but it is a sentiment that seems to be growing and shared amongst those who for the most part feel that Scrum was pushed down on them because someone heard it was a popular Agile method.
Am I right or wrong? I’d like to know what you think!
|
Posted on: July 27, 2013 07:57 PM
| Permalink |
Comments (1)
Get that job using Kanban!
| I like this post from Johanna Rothman about using Kanban to plan out your next job hunt. As she states, finding a job can be quite a complex undertaking:
A job hunt is a big and complex project. You need to decide what to do and when. Who do you interview with? Is it time to iterate on your resume? Do you have enough references? Are you networking “right”? Add the fact that your emotional well-being is affected by your search, and—well, it’s a recipe for low self esteem.
One way to manage this complex project is to use a project management approach that fits the problem. The best way I know is to use personal kanban. Personal kanban allows you to take everything out of your head, get it down on sticky notes so you have the transparency, and then see it move across the board to get to done. You have a way to limit the work in progress and a way to corral those call-backs with the Pen.
As she discusses, its about using the tool to manage that complexity by prioritizing those WIPs that are the most efficient AND effective for your job search. And as the graphic from her example shows, no need for fancy dashboards, just write this down on your job search notebook.
For those job seekers out there, what tools from your PM toolkit either from Agile or traditional are you using to land your next dream job?
A job hunt is a big and complex project. You need to decide what to do and when. Who do you interview with? Is it time to iterate on your resume? Do you have enough references? Are you networking “right”? Add the fact that your emotional well-being is affected by your search, and—well, it’s a recipe for low self esteem.
One way to manage this complex project is to use a project management approach that fits the problem. The best way I know is to use personal kanban. Personal kanban allows you to take everything out of your head, get it down on sticky notes so you have the transparency, and then see it move across the board to get to done. You have a way to limit the work in progress and a way to corral those call-backs with the Pen.
A job hunt is a big and complex project. You need to decide what to do and when. Who do you interview with? Is it time to iterate on your resume? Do you have enough references? Are you networking “right”? Add the fact that your emotional well-being is affected by your search, and—well, it’s a recipe for low self esteem.
One way to manage this complex project is to use a project management approach that fits the problem. The best way I know is to use personal kanban. Personal kanban allows you to take everything out of your head, get it down on sticky notes so you have the transparency, and then see it move across the board to get to done. You have a way to limit the work in progress and a way to corral those call-backs with the Pen.
|
Posted on: July 09, 2013 08:20 AM
| Permalink |
Comments (1)
A tasty concoction of Kanban
| Here's a great inforgraphic provided by toolsforagile.com outlining the ingredients required to make your Kanban implementation delightfully tasty:
|
Posted on: June 30, 2013 11:53 PM
| Permalink |
Comments (1)
Is Agile going postal on us?
| Apparently so, as this article from FCW titled “USPS goes all-in on agile development” indicates that the US Post Office has “one of the largest and most complex in the world, and its growing preference for agile software development methods over its old-school waterfall methodology is having a positive effect on both the agency's bottom line and the mailing industry as a whole.” Started in 2010, they launched Agile as the replacement model for their existing waterfall methodology in four major distribution centers. One of the major pilot projects was the Mail Transport Equipment Online Ordering System (MTEOR) that “allows mailers to order and track mail transport equipment (MTE) online, such as the sacks, trays, pallets and wheel containers that contain mail in transit between facilities.” Looks like by adopting Agile, they were able to achieve some significant results such as a 90% reduction in phone calls to their support center and cost reductions. Due to this, the USPS has now set a policy to do Agile for all IT development projects: Agile software development methodologies and best practices – Scrum, Scrumban, software engineering best practices and the like – are now applied to most every project within USPS' IT shop, Edgar said. In fact, USPS IT has delivered more than 50 projects through agile development methodologies, and 25 projects are currently active. Design teams work with customers "almost daily," and communication between parties is integral to a project's success. So many project successes just three years into USPS' five-year agile adoption strategy roadmap helped spur the agency in March to declare that the agile development methodology will be the standard methodology for all projects unless an exception request is approved. So in a sense, the USPS is going Agile to avoid “going postal” with launching software development projects and I would think that would be a good thing. |
Posted on: June 15, 2013 08:57 PM
| Permalink |
Comments (2)
When Agile fails on a massive scale publicly
|
So here’s this report on the British government’s impending failure of a system called “Universal Credit” which is a way to manage welfare payments in real-time and through a unified entitlement program to lower costs and streamline the distribution process.
Unfortunately, signs are that it is a troubled project even despite the fact that they used “Agile” methods:
In fairness to Agile, it looks as though the method was adopted more in “sprit” and as a ruse, to get the public to think that they were going to use a modern project management method know to deliver software projects efficiently. As the author states, Agile “has been treated as a silver bullet – not as what it really is – just another design methodology – while much of what is supposed to happen with an agile software development project – especially regular and repeated testing of prototypes - has been conspicuously absent.” So of course their decision is to go back to a more traditional approach for the back-end and to use Agile for the front-end, customer facing portions of the system:
Though this will be perceived as an Agile project that failed on a massive scale, one could also view Agile as a method that allowed the failure to be noticed quicker than if they had used a more traditional approach.
Sadly, I’m not so sure if this will build confidence in the public’s overall perception of the government’s ability to deliver projects though.
So here’s this report on the British government’s impending failure of a system called “Universal Credit” which is a way to manage welfare payments in real-time and through a unified entitlement program to lower costs and streamline the distribution process.
Unfortunately, signs are that it is a troubled project even despite the fact that they used “Agile” methods:
Universal Credit is also the world’s biggest ever “agile development” software project and a massive financial and social (and hence political) risk for the government. Unless delivered on time and on budget then the consequences are grave – some of the most vulnerable people in society could be left literally destitute, with all that entails for their personal welfare and social order.
Yesterday the government – at least part of it – finally admitted in public what the rest of us have known for a long time: that the project is in deep trouble.
Universal Credit is also the world’s biggest ever “agile development” software project and a massive financial and social (and hence political) risk for the government. Unless delivered on time and on budget then the consequences are grave – some of the most vulnerable people in society could be left literally destitute, with all that entails for their personal welfare and social order.
Yesterday the government – at least part of it – finally admitted in public what the rest of us have known for a long time: that the project is in deep trouble.
In fairness to Agile, it looks as though the method was adopted more in “sprit” and as a ruse, to get the public to think that they were going to use a modern project management method know to deliver software projects efficiently. As the author states, Agile “has been treated as a silver bullet – not as what it really is – just another design methodology – while much of what is supposed to happen with an agile software development project – especially regular and repeated testing of prototypes - has been conspicuously absent.”
So of course their decision is to go back to a more traditional approach for the back-end and to use Agile for the front-end, customer facing portions of the system:
Some steps have been taken to try to rescue the project. The back end – the benefits calculation – has reportedly been shifted to a “waterfall” development process – which offers some assurances that the government at least takes its fiduciary duties seriously as it should mean no code will be deployed that has not been finished. The front end – the bit used by humans – is still meant to be “agile” – which makes some sense, but where is the testing? Agile is supposed to be about openness between developer and client and we – the taxpayers – are the clients: why can’t we see what our money is paying for?
Though this will be perceived as an Agile project that failed on a massive scale, one could also view Agile as a method that allowed the failure to be noticed quicker than if they had used a more traditional approach.
Sadly, I’m not so sure if this will build confidence in the public’s overall perception of the government’s ability to deliver projects though.
|
Posted on: June 09, 2013 10:44 AM
| Permalink |
Comments (3)