Best practices, lessons learned and advice from your peers in the trenches.
Many business leaders are unacquainted with the wealth of knowledge about how software projects behave. No surprise, they are unable to explain why these projects fail repeatedly, much less do something about it. Here are five fundamental “laws” of software development that all executives (and teams) should understand and follow.
The more rigid an organization is about dates, the less agile it can be. Still, it is legitimate for executives to ask for delivery dates, and there are strategies to meet this need, from time-boxed releases to work-forward planning. Yes, executive visibility is possible in Agile, it just takes some compromise and participation.
Most project managers welcome clear-cut goals and processes. Likewise, they are uneasy around uncertainty, be it open-ended objectives or vague direction. But ambiguity can present an opportunity — to think creatively, to take a risk, perhaps, and try something new that just might lead to an exceptional outcome.
Project costs receive serious scrutiny from executives and stakeholders who use ROI and other financial metrics to judge organizational performance. Here is a checklist of questions to help project leaders and their teams determine the best available options for responding to project cost risks and issues that may arise.
A disciplined team is going to get the job done and produce satisfactory results most of the time, but a motivated team offers the possibility of delivering outstanding outcomes that go above and beyond expectations. Here are some strategies and tactics for motivating your team members.
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.