Whenever the weather allows for it, we like to eat outside. At dinner time in our little courtyard in the city of Toronto, mother nature treated us to a beautiful scene. A few days later it turned into an invaluable lesson...
A mourning dove landed on the fence, looking us straight in the eye. "What a wonderful sight," I thought, "I bet it's eyeing something on our plate." Without breaking the line of sight, the dove flew over to the side of the deck, even closer, testing the boundaries of its comfort zone.
"Roocoo! Roocoo!" A few minutes later mommy dove arrives, a little chick trailing inches behind her. The family reunited, they waggled to an open space a bit further away, while we watched the scene unfold at a safe distance. By now we realized that daddy had scouted the environment, checking our reactions to his proximity. He must have considered us safe, the little one would not be harmed.
To our surprise, the adults took off, leaving the little one alone. Stunne...
The Greek philosopher Heraclitus was onto something when he said many years ago that
ange is the only consta Chnt
A saying as true today as it was for Heraclitus in Ancient Greece.
Today, businesses are impacted by change. Competitors introduce new capabilities or services, customers' loyalty shifts from brands towards value propositions, and new and exciting players disrupt the market altogether.
Recently I was on a call chatting with a group of senior leaders and the topic of work-life balance came up. More explicitly, how “now he seemed to have so much less time at the weekends”. Asking a few questions of the gentleman who brought this up identified that he had been newly promoted to a VP role.
Which got me thinking about the challenges as you move between roles in larger organizations. Expectations change as you move from an IC to manager to director to VP or above.
So I thought I’d jot down a few thoughts on the matter.
Let’s talk about the elephant in the room. Most transformations do not deliver upon their intended results. Many of these transformations use sound agile methodologies, yet they fail to deliver on the expected results. DevOps came along and refocused the effort, but still, we run into difficulty with transformations stalling or even failing.
Current thinking puts the development (aka. delivery) team front and center in the transformation to rapidly enable the delivery of value to customers. For a team, they need to be able to have all the right skills and capabilities at the disposal so they can own their delivery processes. In complex environments with multiple architectural principles at play, this can be difficult to achieve. To cope with this, we create another team, the platform team, to enable the delivery team.
The question is, do I need a platform team?
How many of you have been through something labelled as a digital transformation in the past 5 years? Many hands go up, and several people groan. It seems like we are in a constant state of transformation, which is true. Change is the new normal and transformation is the grandiose title given to the work we build around it.
Yet many transformation efforts stall or even fail. We encounter many reasons for this, including market pressure, hierarchy and blame culture. Even gut instinct being the primary way to make decisions comes into play! Core to most digital transformation efforts is aligning technology to business goals, which often creates problems with delivering the desired change due to their different goals.
When technology departments drive the transformation, they often need help explaining the value. Ensuring stability to reduce rework through innovative techniques and tools may not resonate. Still, we do require change through transformation for our businesses to thrive. With...
As health specialists and governments encourage employees to work from home en masse, many employers start fearing the impact on their teams’ productivity. After all, the agile manifesto states as one of its principles:
e most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Th
Are we doomed to return to less agile ways of working? Will we see productivity plummet? Will we see new value being released only ever so often?
Let’s first start with this breaking down this statement.
The main difference between online (or remote) and collocated teams is the way in which they communicate. Collocated teams benefit from what Alistair Cockburn calls osmotic communication. You could explain it as transfer of information and knowledge by virtue of being in physical proximity with your team, where all work is done, where all frustrations are voiced and all intentional and unintenti...
Often when we first engage with organizations, we find they enter the conversation with a clear idea of what their problems are. Sometimes they get it right and other times - more often in my experience - they are focusing on their own belief of where the problem lies.
For example, if the problem is the deployment process, why does the automated script take 5 minutes to run. Having successfully worked with development teams to automate deployments of their major platforms, being told deployment is the issue seems like the wrong place to focus. If it still takes weeks to get code into production, the problem lies elsewhere. Perhaps our test verification takes five weeks?
Ok. Well, if deployment of code isn’t the issue and testing is, let’s focus there I hear the cry! Well, let’s see…