When becoming agile, there are many ways that we start to look inward in order to change how flexible we can be. We start to think about work differently. We think about how we collaborate together. We think about task, story and epic level things. We also ponder time itself. Is there a placeholder event for that? Is this the appropriate time? Is the time-box up? I remember the high school teacher’s frustration at having students look eagerly at the clock – anticipating the moment when the bell would sound the end of class. Ultimately later in the year, the note underneath, which was posted and read “Time will pass. Will you?”
There are things that are run by clock time. In the agile world we set limits on meetings and sprints Many organizations still account for hours. Things that are run by the clock. It lends a sense of urgency and there is a certain puzzling in order to fit activities and interactions to fit appropriately. Time does not stop. It marches. What does change though – is our perception of time. Some moments whiz by or instead as Shakespeare said slowly drags on and “Creeps in this petty pace from day to day, To the last syllable of recorded time”. When our days are managed by the clock, I often wonder if this alien and measured arbiter of fate sometimes robs us of an empowered position. Some teams often measure a sprint burn down with hours remaining (Which I’ve previously talked about here) .
When timelines are populated by events they often give us a sense of achievement and better context than Chronos‘ stamp of numbers. I am looking for a task to complete rather than time to run out. Choosing achievement over activity and hallmarking instead by the memorable actions which have culminated in a sense of completion. Sometimes ending a day in a ‘good spot’. Event time seems to allow for creativity and innovation that spark and motivate just a little more. Doing something Better than before, not just the same way over and over. Is event time always better? probably not as with all things there is a balance. It will Clock time that helps us determine if something ‘unsustainable’. But, again, only because we haven’t achieved the desired events. A Team might measure tasks, not as hours remaining, but rather as events – only wanting to know if they are in progress or done. A retrospective timeline will often be measured in 3 ways – the chronological timeline (1) earmarked with events (2) and our reactions (3).
The matrix first coined the term, being fluid and moving faster than we thought possible. Unfortunately it always seems to be during crisis moments. Whether on a six story drop on an amusement park ride or in front of a release review. Our brain registers everything and goes into a hyper protective mode. It’s sometimes hard to remain calm and in a problem solving in a panic driven environment. At times the uber-urgency brings out some of the best in our teams in an almost Apollo 13 type of way. There are no lives on the line, but the sense of responsibility doesn’t seem any lessened. It usually takes longer term investments in teams of people to make critical and good decisions. To support those teams we invest in infrastructure and technologies. We let them adopt lightweight processes which enable them to move quickly. Bullet time is not a sustainable thing. But some of the best days are briefly ventured here, when the team pulls together and works itself out of a crisis. Even better when the team plans to avoid the same thing from ever happening again and moves back into Clock or Event time.