Negotiators in this story followed the rules and ethics of the game. The goal was to maximize the gain of their respective organizations. There was no compromise on integrity. At the same time, the instinct of a youngster and the wisdom of a veteran collaborated to take the game beyond zero-sum and made it win-win…
We have unparalleled opportunities to rethink how we work as an individual and in teams—and the pandemic has also highlighted the true essence of what it means to be a human being in this globalized world. Discover five patterns of the “new normal” as we adapt to a modern way of working.
Successful portfolio management requires sound processes for building consensus on what is important and how project results will be measured. Here are four value-based models to facilitate better decision-making.
The typical response to tough economic times is for IT leaders to make across-the-board cuts. While the cost savings are immediate, they are drastic, one-time fixes that introduce risk and don't position the organization for future survival.
Value-driven projects differ from plan-driven projects in significant ways, including how teams are formed, how funding is obtained, how scope is determined and how solutions are achieved. They seek valuable rather than predictable results. Here’s a roadmap to making the switch.
Velocity is an agile planning tool, not a measure of productivity. Its purpose is to help determine which stories will fit into a sprint, and how many sprints remain until a release is ready or the project is done. Velocity is not about team efficiency or effectiveness, and treating it as a metric to continually improve is another Agile Anti-Pattern.
There are many reasons why it isn't a good idea to “increase velocity” as a proxy to show the team is “doing more.” If your goal is to figure out how to improve efficiency, or simply increase the output of the team, then using the velocity metric isn’t the right way to go about it.
Though there is lot of bias toward increasing velocity every iteration to release more features faster, if there is no attention to quality, the system will soon become fragile—and will not be able to house scope changes in the future. How do we balance these forces?
After more than 20 years in the financial services industry, this writer thought he knew exactly what to anticipate moving into his new role as a software vendor project manager. He was wrong...