Hybrid isn’t coming, it’s already here. And the reason that it is becoming so popular is obvious: It works. That means that organizations must not only embrace the concept, they must ensure that their project delivery environments allow it to be used.
One common failure pattern in creating agile development teams is taking a regular software tester, assigning them to the new team and expecting them to perform in new ways that elevate the team to high performance. What does a good agile tester look like? What should we expect of them? And how do we find them?
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.
Agile processes can offer rewarding advantages to traditional software development, but they take time to adopt properly. New teams will likely encounter conflicts and confusion during their first sprint retrospective. Here are five lessons learned that can help your next sprint avoid some common pitfalls.
Agile methods are powerful approaches that bring many benefits to how we undertake project work. However, they are not immune to misuse or failure. The following list of five common pitfalls is often seen in organizations switching to agile.
The discipline of project management tends to be relatively stable as processes and methodologies are well established. However, just as technology and business models change, project management adapts over time. Here are some trends within our industry that are likely to gain momentum over the coming year.
Sink or swim! Taking over a dysfunctional project team can be a very frustrating yet exhilarating experience. This article summarizes some “rules of the road” that should help you navigate through shark-infested waters--with the result being a highly motivated department or team delivering quality projects on time.
Like baking, how we combine elements results in very different outcomes, each suited to different occasions (or just a useless mess). This article explores the reasons and results of a couple of popular hybrid project approaches.
The adoption of lean thinking or agile principles should not be approached as a project with an end, but rather as a journey of continuous improvement based on experimentation and developing problem-solving skills. And the concept of “impediments service” is a key component.
Retrospectives can be one of the most impactful parts of agile delivery, identifying and addressing problems quickly and in a way that has a good chance of success. If you aren’t fully leveraging the process, then you are undoubtedly leaving opportunity on the table.
|
I did this thing on the Ottoman Empire. Like, what was this? A whole empire based on putting your feet up? - Jerry Seinfeld |
