Agile is about empowering teams and individuals. The roles defined by Agile are: Product Owner, Scrum Master, and team member. Not listed? Project sponsor.
That said, organizations often have established practices around designating a sponsor or two when a project or program is initiated. How do these two worlds meet? Should Agile teams have sponsors or not? Can a sponsor provide value to an Agile project?
Read More
For too many people, the concepts of “acting as a responsible CIO” and “taking risks” are mutually exclusive. A Traditional CIO is accustomed to a world where if nothing breaks, their job is safe. If they don’t touch anything, they can’t break anything. In this paradigm, taking risks is unwise.
In my opinion, rampant risk avoidance is the reason CIOs now lose their jobs at the second highest rate among the C-suite. Inaction—or maintaining the status quo—carries a much greater threat to the CIO (and the organization) than does taking an active stance and assuming the associated risks. In the digital age, where IT is the business, being CIO is like playing quarterback: if you stay in the pocket long enough, you will get sacked. You have to make a move.
Read More
In work, as in life, we can’t succeed on our own. In fact, the cornerstone of execution, change, and success in any organization is not a single person, but rather teams of people who work together to make things happen.
But why is it that some teams knock it out of the park while others struggle? The secret lies with organizational leadership and management—are you giving your teams what they need to succeed?
Read More
Sure, the first days in your role as CIO are critical. Advice abounds in books, blog posts, and presentations for how to approach your initial 90- or 100-day period. These recommendations are compelling and directionally sound. In reality, it’s rare when a CIO nails their first 100 days in perfect form. But that’s ok! The real issue is what you should do after the first 100 days are up.
Read More
Trust is the grease that keeps a team running smoothly. One of the most effective and low-cost ways to improve the delivery, performance, and morale is to gain the team’s trust. As a Scrum Master, it’s your responsibility to build trust with your team. A team that trusts their Scrum Master has an advantage over others. Broadly speaking, teams perform better when they feel they’re in good hands.
Scrum Masters can seem like outsiders, as you tend to interact with the team, not with their work. The dynamic is exacerbated during Agile transformations: Scrum Masters who are brought in to work with a team that is used to a waterfall approach can struggle to gain the team’s trust.
Here are 5 ways to connect with your team, and demonstrate that you are here to help and support them:
Read More
There is a new type of CIO on the scene: the Transformational CIO. Transformational CIOs focus on external customers, innovate, think about the top line, drive business process evolution, and change the culture of the entire organization.
The almost-extinct type of a CIO—one we would all like to forget—we’ll call the Traditional CIO. Little is written about the misery of the Traditional CIO. Traditional CIOs are focused on technology first, take orders from internal customers, don’t rock the boat, and diligently reduce IT spend by 10 percent year over year, using band-aid solutions to keep outdated technology operational.
Read More
When hiring new team members, most interviewers discreetly study applicants to see if they would pass The Airport Test: “Could I get stuck in an airport for 8 hours with this person and not lose my mind?!” We recently took this idea to an entirely new level.
Read More
The Agile methodology has been widely accepted and implemented in many organizations for various goals. Most use Agile for project execution and product development. We even advocate using an Agile-based iterative engagement model for vendor management to minimize the risk of getting locked into long, inflexible contracts, and to prioritize outcomes over arbitrary task lists.
Many executives still think an Agile methodology would never work in their organization. Some have even attempted to implement Agile and were not happy with the results. Agile flops tend to fall into one of two categories: The organization either did not implement the actual Agile methodology, or was not ready for it.
Read More
We are big believers in an iterative model for vendor engagements. It’s a novel concept for some organizations. To determine if the approach is right for you, familiarize yourself with the potential risks and rewards for both the client and the vendor.
Read More
Agile is now being used far beyond its original purpose, which was software development. We see organizations apply Agile methodology to any project or program where the end result is a continual work in progress.
Come to think of it, my son and I use an Agile approach when we go fishing. We know we want to catch a bunch of fish, but we don’t know what kind or where, so we move our canoe around the lake all day based on our success in each spot, wind direction, time of day, and other factors.
Abraic exercises an Agile approach for our internal innovation program. Our R&D group is working strictly on a high-frequency, trial-and-error basis in one-week sprints. This minimizes cost exposure and allows us to make adjustments based on the latest findings.
Another area where an Agile approach is very effective is vendor engagement. The predominant practice to date has been to take an ambitious high-level scope and hand it off to a chosen vendor by means of a complex, long, and expensive contract. Yet, there are many cases when the project requires a significant redirection, including changing the vendor, utilizing in-house resources, re-scoping the project, putting the effort on hold, and so on. We end up having a to make a tough choice: make minor tweaks and complete as planned even if it doesn’t match our expectations or try to renegotiate – a lengthy and painful endeavor that may involve legal and oftentimes damages relationships.
Read More
