• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Agile Buddha

Demystifying Agile, Getting to its Core

  • Our Blog – Agile Buddha
  • Agile Workshops and Certifications
  • Agile Commune – Join Here!
  • Webinars
  • Contact
  • About Us
  • Show Search
Hide Search

Agile

When is a Good Day to Start a Sprint?

by Avienaash Shiralige 4 Comments

My first reaction would be Monday! Week is just starting and definitely good day to start something new. You are right! But my suggestion would be to rather focus on sprint ending day then starting. Ending on a Friday is not I have seen worked very well for many teams.

Let’s check out few reasons for the same:

  • Friday being last day of the week and team is quite tired by then. Hence chances of making a mistake in rush to complete a sprint is higher
  • Many times last few changes go untested before Monday demo which is a high risk
  • I have seen team working over weekends to finish and push last minute changes to code repository. This is absolute NO, as I want my team to relax and also these changes are not known to rest of the team and it is not tested. This breaks Scrum philosophy.
  • Most important thing, people get freedom to take long weekends as they would not miss Sprint Review and Sprint Planning which I feel are two most important Scrum team ceremony where we want everyone on team to be there.
  • Lot of Public Holidays falling on Monday or Friday would not disrupt the team much.

Hence my suggestion to the team I have worked with is to go for starting mid week and ending mid week. Even if you have to stretch a bit to finish some tasks, team would not hesistate to do it during mid week and also keep in mind as per research Wednesday and Thursday are most productive days of the week too!

Teams moving to this schedule have seen reduction in defects, increase in quality of code and also quality of demo improved substantially. Above all this I have seen team being less stressed and hence better productivity.

In addition to this if teams are working in distributed agile set-up(say Product Owner is in US west coast) and team is in India, then starting sprint on Monday may pose few challenges like Product Owner being available for sprint planning on his Sunday evening!

So do consider your team set-up, how they are structured, their maturity, Product Owner & Stakeholder availability etc to see what day suits well for you. But don’t stop experimenting around this!

The Hidden Obstacles to Agile Transformation Success

by Avienaash Shiralige 5 Comments

Let’s say one day you wake up and think, ‘I want to be healthier.’ You decide, ‘I’ll start eating an apple every day.’

You stick to this routine for months while continuing all your old habits, such as staying up late, eating junk food, drinking alcohol, smoking, and so on.


Do you think having all these habits and eating an apple a day will keep doctor away?

Definitely NO.

And after a while you might even get disappointed and frustrated, and you will decide to stop eating apples claiming that “a healthy lifestyle simply doesn’t work for you” or “eating apples is not really helping you”.

[Read more…] about The Hidden Obstacles to Agile Transformation Success

Strategy Making Should be More Agile

by Avienaash Shiralige Leave a Comment

Companies find it very tough to survive in current fast changing markets. You can not sit on a one year plan assuming that it will strike gold! You need to monitor your strategy implementation, measure it and make necessary changes. Some leaders who are extreme agile(giving complete autonomy) get this wrong and they pay the penalty of being extreme agile. So it is a balanced approach that you need to take depending upon the culture and maturity of the hands at work.

You can read my earliest post “Do You Think Your Strategy Would Succeed?“

Why Agile is Like Doing Yoga

by Avienaash Shiralige 4 Comments

Agile is so natural that you can apply them into any discipline, in your personal lives, in other industries etc. Why we are seeing mass movement within and across companies to adopt agile. Because people are realizing it as natural way of building software in this imperfect world. My experience in last 7 years taught me that it is like doing meditation or yoga. It relies a lot on honesty, rhythm, openness, flexibility, sustainability, complete control on self etc.

Please check my earliest post on the same. Scrum is Yogic way of doing software development.

Good Culture where ‘Self Organized Teams’ Thrive Contribute to Better Productivity

by Avienaash Shiralige 1 Comment

Why everyone talks about self organised teams and find it extremely difficult to build. Many people I talk to, work with find it insane when I say that we need to give autonomy to teams. Hence it is important to find leaders to the lead the organisation who are open to change and ready to give away their control. Also find right developers who can think and act more than just doing coding.

Here, I would like to discuss how good culture where ‘Self organized teams’ thrive can contribute to better productivity.

India is one of the most favored and favorable offshore/outsourced destination in the world – thanks to the mass scale of engineers it produces. But now the time has come for us to see how we can better productivity – without sacrificing quality (that goes without saying), which will contribute directly to our margins and net profit. The game has changed from just scaling and being cost- effective to how we can provide maximum business value with less effort.

It’s high time we gave preference to productivity and quality rather than just harp on quantity. There are numerous factors that contribute towards productivity.

Here, I would like to discuss how good culture where ‘Self organized teams’ thrive can contribute to better productivity.

Self-organising Teams

Steve Denning, in his research, found that “most of the high performing teams were not manager-led teams. They were teams whose management had deliberately stepped back, or were inattentive, thus enabling teams to self-organize”

Compared to them, the ‘self-governing’ teams did not demonstrate high-performance even on a single occasion. Their struggle for “what to do” always came in the way of their performance. Hence you need leaders on the team to set overall direction in technology, process, and business/product.

Most ‘Self-organized’ teams have the following characteristics

  • Ability to commit to the sprint goals together
  • They work aggressively to remove impediments to their progress
  • Collective focus on highest-priority stories
  • Choose to pair wherever required
  • Freedom to take risks and to say NO

All the above reasons help in generating lot of energy and passion for ‘self-organizing’ teams, which eventually leads to high productivity.

Now let’s look at the table, which is the result of Geert Hofstede’s years of research in this field. He has defined multiple parameters for us to understand the culture of different countries.

One of the parameters of research was PDI (Power Distance Index). It reflects the extent to which less powerful members of a culture accept that power is unequally distributed and they don’t resent the authority easily. This index varies across cultures with Denmark showing highest resentment while China the lowest. This stark variation across countries could be a very interesting and revealing study by itself.

Country PDI
China 80
India 77
Brazil 69
US 40
Netherlands 38
UK 35
Finland 33
Norway 31
Denmark 18

A PDI score of 70+ for India clearly indicates that people are far less likely to resist the changes – whatsoever – suggested by authority. Not a progressive sign, eh? This applies to teams as well.  They are more susceptible to if we hire a command and control manager/leaders and team may NOT resist this openly.

*Building an organization which has self-organizing character, with absolutely no hierarchy is immensely tough – more so – as it’s a constant struggle against our own culture/mind set. *

Preserving this self-organizing culture while we scale is a battle and hence it is extremely important who we bring on-board from middle to senior management. He/she should be a person who is open to work as servant leaders.

A key practice for hyper productivity teams is to have servant leaders like product owners and agile coach who provide team leadership as well as work for and with the teams to actively remove impediments.

A common pitfall that self-organized team face is the perception that they do not need any management. While it is true that ‘management’ –in its mere traditional roles – allocating tasks, monitoring progress etc – is not required for self-organized teams, the need for GOOD LEADERSHIP is paramount. A person, who is progressive in thinking, shows agility, open for change, and accept newer ways of doing & who enjoys giving and taking freedom.

Good leadership on new agile teams includes

  • Guiding them on collaborating effectively with customers
  • Showing way
  • Mentoring them on agile principles and practices
  • Gradually passing on these roles and responsibilities to the team members

Leadership on new teams is usually taken up by Agile coaches (Scrum Masters, ex-Project Managers that have successfully acquired an agile mindset).

But, a common feeling among the managers is: ‘Who moved my cheese? I see this as an opportunity for them to explore new avenues in leadership, scaling different levels in project management then monotonous tasks allocation and reporting.

How effective are your teams self-organization?

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 16
  • Page 17
  • Page 18

Primary Sidebar

LikeBox

Tags

5 Whys Acceptance Criteria Adoption agile Agile Culture Agile Estimation Agile Offshore Agile Teams agile testing Agile Thinking Agile Transformation Agility Appraisals ATDD Automation Backlog Grooming BDD Big Picture business analyst Capacity Planning case-study code quality Collaboration Daily Scrum DevOps distributed agile Distributed Scrum Estimation Good Practices kanban kanban-mythbusters lean Metrics Planning Poker Prioritisation product owner Scrum ScrumMaster Sprint Sprint Demo Sprint Retrospective Story Point Story Points Sustainable Pace User Story

Categories

  • Agile
  • Agile Leadership
  • Agile Testing
  • Agile Transformation
  • ATDD
  • BDD
  • Continuous Inspection
  • Culture
  • DevOps
  • Distributed Agile
  • Estimation
  • In Conversation with Tim Ottinger
  • Java
  • Jira
  • Kanban
  • Lean
  • noprojects
  • Patterns
  • Presentation
  • Product Owner
  • Scaled Agile
  • Scrum
  • Software Metrics
  • Testing
  • Testing Practices
  • User Story

Copyright © 2025 · Malonus Consulting LLP

  • Email
  • LinkedIn
  • Twitter
  • Facebook
  • Privacy Policy