Many organizations have struggled with their early agile experiments. Due to the issues faced, they typically cannot answer the simple question: “Are we ready to go agile?” This first article examines the factors that indicate whether the sponsoring organization is ready (and able) to modify the way it works to increase the chances of a successful agile project.
With over half of companies using a blended agile and waterfall approach to development, it’s critical to be aware of how an agile approach affects planning and alignment with the overall business strategy. Here are the most common challenges in enterprise agile development--and some tips for how smart companies are navigating the new landscape.
Why is team ownership important? It is essential to agile team success because individuals thrive on ownership. With ownership, you have a stake in the game and push to find the best solution. The difficulty is that most corporate cultures have command-and-control leaders. Here is some help...
For agile teams, a traditional PMO can seem to Present Many Obstacles--but it does not need to be that way. With some alignment and time invested, they can be useful advocates.
What are your big goals? Productivity? Speed? Happiness? All of these are understandably desirable. They also share another attribute: They all are best achieved by seeking other, lesser goals rather than by seeking them directly.
Agile is as much about process as Disney theme parks are about Mickey Mouse (i.e., very little). Yet people seem to focus on the process, probably because it is easier than capturing the true intent of agile. Here we peel back the facade of process to uncover the agile heart that beats beneath.
Agile project management, and particularly Scrum, can become overwhelmingly consumed by methodology, jargon and rules. This is just the opposite of what was originally intended for agile-lead projects, and it is the communications part of our role that is so important.
The Agile Movement continues to pull in project managers who have been steeped in traditional approaches. In this PM's experience, relatively few successfully make the transition. Here’s why…and what we can do about it.
We all need some help sometimes when introducing agile methods into a traditional organization. Fortunately, a new guide to ease the transition is available. The recently published Software Extension to the PMBOK Guide Fifth Edition acts as a Rosetta Stone for mapping and replacing traditional approaches with their agile alternatives.
|A.||Not every team needs to be agile. Wait until the larger organization changes enough that you think it can be successful. In the meantime, change nothing.|
|B.||Your organization can benefit if it becomes attuned to the agile philosophy. Change your IT practices and the rest of the people will eventually automatically alter the ways they support you.|
|C.||Change your team now! Ignore the rest of the organization. As long as you and your co-workers create agile artifacts, the value stream for the business will automatically flow.|
|D.||Agile teams planted in an indifferent or hostile environment cannot grow and flourish. Figure out in detail where your organization stands on a readiness scale, and then work to move it toward a more supportive environment.|
Is your organization embracing agile, or rejecting traditional approaches? People look to agile to be more effective than a waterfall-based approach, but to move to agile only because the current approach is failing is shortsighted. In this article, we try to identify a few things to help ensure that agile is a success.
As the use of agile methods spreads into larger organizations, senior managers struggle to decide their agile adoption strategy. Here are three stories from three large Canadian banks who each took a different adoption approach.
While there is almost unanimous agreement on the importance of teams, the vast majority of people don’t like to belong to them. This raises a loud warning for you and your agile team, one you must address proactively, because an agile project succeeds or fails on the health of the team. Maybe the GCCR Plan can give your team members wings that fly.
|A.||Management does not care what team members believe as long as they turn around work more quickly than they did in the past. Leave people to think what they will.|
|B.||In addition to the team rules and the agile methodology process rules, tell people each day what they are to think about the work they do and how they should view others.|
|C.||You can’t mandate change. You can only find a fun way to demonstrate and remind people on the team about the premises of agile philosophy.|
|D.||If your team won’t quickly adjust to knowing and following the agile philosophies, this approach to doing projects will fail. Return to traditional project management practices.|
When approaches work well, it is natural to want to replicate them. However, scaling a process is not as easy as saying “Do more of it!” Here, we examine some strategies and anti-patterns for successful scaling.
Do the skills required by each function make it almost impossible to be a successful PM and ScrumMaster? Our writer had one theory as he started his musings...and ended up somewhere else entirely.
While each organization is unique and struggles in its unique way, there is a common thread: they haven’t prepared adequately for their agile journey. What should you bring on your agile journey? If you’re already traveling, what should you add to your luggage? Here are the top 10 items...
Virtual teams may well be the next step in the evolution of work. So it is interesting to ask if today’s management principles and processes are optimized to support them. To help answer this question, let’s take an illustrated tour of work through the ages and also review how management has progressed along the way.
With the shift to a more agile, team-centric organizational structure, singling out individuals can become a cumbersome and stressful task for even the best and most experienced managers. In this article, we cover how rewards can actually backfire--and give you three rules of thumb for rewarding your best performers.
Some managers claim that agile approaches don’t work in large organizations because they have tried--and failed--to deploy agile methods in their company. This article describes one of the major underlying causes for these failed adoptions and makes suggestions for resolving the issue.
Imagine for a moment that interest in your project catches on like crazy. Hundreds of people pitch in to help you meet an impossible deadline. Complete fantasy, right? It can happen, and it did. And the takeaways for your agile project are real--and powerful.
It's hard to know if we're producing systems as fast as we could produce them. We can, after the fact, always identify ways in which we "wasted" time without contributing to our desired outcomes. But why can't we identify which will be waste before the fact? Because we want to go as fast as possible!
According to various surveys, many IT projects worldwide use agile methods. What the surveys don’t tell is that many of those projects suffer from the typical ailments of traditionally run projects: compromised quality, technical debt and missed deadlines. Why is that? And what can you do about it?
The decision to get agile training is a question that’s part of a bigger one: Whether one is ready to adopt agile practices and principles wholeheartedly. When are you ready? There are four fundamental questions you have to ask yourself before embarking on an agile training program.
Are agile practices themselves ever so rigid that they become stifling rather than liberating? Sometimes, strict adherence to an agile framework can cause problems for project teams. Be on the lookout for these issues...