Skip to main content

4 Dysfunctional Behaviors and Scrum Framework

In "4 Behaviors That Can Save or Destroy a Project" blog post, I described four behavior which they can impact a project delivery time, quality and cost. These behaviors are: Student Syndrome, No Early Work Transfers, Parkinson's Law, Polychronicity. However, project management frameworks such as Scrum provides simple and effective tools and techniques to deal with these type of behaviors. Such tools and techniques are: Time-boxing, Volunteerism, Continues Self-Inspection, Transparency, Continues ordering (prioritization) and Team Estimation.

Everything in Scrum framework is time-boxed. Every meeting is time-boxed, every sprint or iteration is time-boxed. There is no deadline, but there are many time-boxes! Teams using time-boxing are way more productive than teams using deadlines. There is a shift in mindset from "We need to work hard to meet our deadline" to "How much we can get done in the given time". This is very basic but very powerful change in mind set.
At the start of planning in Scrum, team tries to evaluate their productivity by looking into their past performance and the environment they work in and skill sets they have (Velocity), and then they decide how much they can accomplish in a time-boxed period, they also decide what is the duration of that time-boxed.

Teams, who use time-boxed, look at things with more accountability and with a scenes of ownership. They decide what they can get done within a specific period of time and then they commit to it. Teams who have deadlines are always disagree with deadlines as they do not see the ownership and self-commitment.


Daily Stand up meetings in Scrum is a way of self-inspection. It allows every team member to share his/her accomplishments, plans and obstacles on daily bases with other team members (and sometimes with product owner and customer) in full transparency. If a task is close to be completed then others will know and will act (avoiding No-Early-Work-Transfer). If one shares his/her plan and accomplishments on daily bases with others who do the same thing with him/her, then such individual will not be trapped in Student Syndrome. Imagine a class of students who must share their exam preparation works and questions/obstacles with other classmates and teacher on daily bases until the exam day, I guaranteeing you that everybody will get an average of B if not A+!


Team shares their progress to whoever is interested, they usually put them on a wall (virtually or physically). They review it on daily bases and make adjustment if necessary. Such transparency give ownership and responsibility to team members and as result high motivation.

When you combine such simple techniques of Time-boxing, Volunteerism, Continues Self-Inspection, Transparency, Continues ordering (prioritization) and Team Estimation that Scrum provides then you have a team that never falls in to the trap of the four dysfunctional behavior. Although it may take some time for the team/organization to reach to such maturity level. The Good news is that, tools are there and path is clear!



Post a Comment

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Ingredients of Startup Failure

I have started and worked on several startups in the past 16 years. When I look back, I find the following patterns appearing again and again in every unsuccessful startup that I was involved in.

Here is the list of patterns, and they are not in order. I wrote them as they came to my mind:

Giving Up Soon: We gave up soon. Sometimes at the start of success we stopped. At one startup we started to make small amount of money after several months, and then we stopped! To be fair, we stopped, because the team collapsed, but anyway we stopped at the moment that money started to come in.Not Putting 100% focus: We did not put 100% effort into it.  For some of us it was the secondary job, and for some of us it was the last thing on the daily agenda!Not Hustling: We did not hustle.  Some of us took care of our comfort instead of hustling.  Not Passionate Enough: Some of us were not passionate about the problem we were trying to solve, or customers we were trying to serve, and the change we migh…