Managers in agile organizations remain not only relevant but critical to supporting high-performing initiatives. They recruit and construct teams, gather and provide feedback, guide career paths, and coach results. If a manager isn’t engaged in these areas, it’s likely no one is, and the team will eventually suffer.
The best way to market anything is to explain the solution you have to a problem, and it turns out that user stories are a big help in that effort, says Agile Marketing Academy’s Nic Sementa, joined by special guest Alistair Cockburn. But writing user stories for ad campaigns is different than for software. [39 min.]
Organizations that see Agile as a way to remove a layer of management are either missing the point or at risk of missing a huge opportunity. Specifically, the role of a software development manager takes on a different and often more important role in an Agile framework.
Agile teams are typically small and ideally stay intact, improving as they bond. But sometimes specific expertise needs to be brought on board. There are several valid reasons to do this but also downsides, from dependency to disruption. Here are three steps to mitigate the risk of adding an "outsider" to your Agile team.
Business leaders lack confidence in their ability to navigate digital transformation, according to a new global survey. Barriers to building an Agile organization include disconnect between project managers and executives, lack of transparency, poor communication, and overreliance on spreadsheets.
Where will Agile transformation drive the most value in your organization? Probably in the areas where business conditions are changing rapidly and customers or stakeholders expect continual improvement in your service or product. Here is a helpful exercise to better identify those areas that could most benefit from an agile approach.
Agile approaches are meant to maximize flexibility, while minimizing costly disruption to projects. In practice, they typically accomplish the former better than the latter. Here are six strategies to help teams manage interruptions and mid-sprint changes. Finding the right balance among them is the key to success.
Once a non-agile customer or sponsor begins to see the benefits of an agile approach, it is critical to reaffirm their leap of faith and build trust through demonstrations that deliver working product, facilitate open discussion and change-focused feedback, and keep the project on track.
Agile is about adapting to change, not completely abandoning documentation or dismissing helpful planning and estimating inputs. Here is a look at how the benefits of an agile approach can shine brighter when used in conjunction with a fundamental development practice such as sizing.
What happens to your agile principles when a customer or sponsor insists on knowing the cost and duration of a project before you even start? It’s a common quandary, but there are ways to show a non-agile client the benefits of going agile, starting with a discovery project.