Best practices, lessons learned and advice from your peers in the trenches.
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.
When assessing and comparing technology solutions to support your project management efforts, a wide range of potential features must be weighted and rated, along with vendor fit and cost. Use and customize this software evaluation matrix to guide your selection process.
We should leverage technology to free our teams to focus on higher value work, but if our devices become disruptive, or replace sound judgment, we are increasing project and organizational risk instead. Rules for using technology can help, but the biggest impact will come from showing teams by example.
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.
A project’s goals and a project manager’s success measures are often conflated, but they’re not the same thing. Goals come from stakeholders; they are outcome-driven and focused on organizational impact. Success measures demonstrate the work achieved. Here’s a closer look at this key distinction.
Project leadership is about finding the “glue” that binds a team to work well together. It starts with gathering information about team members, listening to their concerns and knowledge, finding the common threads that can unify them, and then empowering them to execute the plan.
How many of your projects stagnate before they ever really get going? How many kick off with grand expectations but fail to deliver even minimal benefits? Here is a back-to-basics framework for starting and scaling your work, be it a process, product, system or entire business.
Project teams in regulated industries must get compliance requirements right — a company’s reputation and legal standing depend on it. Here are eight best practices to help PMOs, product owners and business analysts to better understand complex regulatory environments, interpret rapidly changing regulations, and develop clear, complete requirements.
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.