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.
Top agile organizations favor a product-centric model of execution over a project-centric model. They chase value instead of predictability. Let’s look at what’s wrong with plan-driven projects, and why it’s better to organize your efforts along business capabilities, supporting capability teams instead of project teams.
Michael Tibbert — a servant leader of various teams at a technology provider to the energy sector — discusses how he made the transition from PMP-certified project manager to Scrum Master, and how he advances agile processes beyond software projects into other areas of the organization. [32 min.]
During an organization’s transition to Scrum, significant benefits can become apparent early on, as everyone learns the principles and processes of Agile management, including stronger communication, transparency and leadership.
A new report from Project Management Institute highlights six foundational practices for establishing an Agile culture, including rapid response to opportunities, shorter review-decision cycles, elimination of organizational silos, alignment of capabilities to strategy, a focus on change management, and integration of the customer’s voice.
Most project management processes — assigning deadlines, monitoring resources —originated in IT and manufacturing. But they don’t translate well when applied to the creative world of an all-digital agency where products are often borne out of inspiration. So how do you manage a project that is dependent on spontaneity?
At some point during an Agile transformation effort, individuals and teams start feeling better, worse or indifferent about the changes taking place. Beyond the mechanics and mantras, what should organizational agility "feel" like? Here are seven “DNA markers” to gauge if you're on the right track.
Agile methods have the capability to transform IT-business relationships and positively impact value delivery. But IT leaders must be dedicated to the culture change necessary for success. Here are 10 guiding principles you need to know about agile development.
Agile anticipates being wrong, or at least not exactly right, and the same principle applies to any organization becoming agile. The best approach is to simply get started and commit to the fundamentals: prioritize, re-plan, release frequently, seek constant feedback, and trust enough in the cycle to continue.
Scrum Alliance CEO Manny Gonzalez discusses key takeaways from the just-released 2015 State of Scrum Report, including the growing acceptance of agile principles at the management level, the evolution of hybrid models, the increased use of distributed team, and future challenges such as improved metrics. [18:00]