Many organizations have struggled with their early agile experiments. Due to the issues faced, they typically cannot answer the simple question: “Are we ready to go agile?” This first article examines the factors that indicate whether the sponsoring organization is ready (and able) to modify the way it works to increase the chances of a successful agile project.
Advance Your Career
Agile PM is one of the emerging ‘hot topics’ in the PM domain, and given the breakdown of the ‘plan – then execute’ model in Project Management, the adept project manager is constantly having to improvise to deliver against changing project deliverables. This webinar considers and compares Agile PM and Organizational Improvisation, and offers assistance with moving PM execution from the ‘tools and techniques’ based PMBOK® model towards techniques better equipped to deal with today’s ambiguous and changing project environments.
In this webinar you will gain a solid foundation of agile and see how ANY project can benefit from some core practices common to organizations that are agile
Save Time With Tools + Templates
The Three-Sentence Project Skinny is a concise summary of the purpose of the project. It addresses the what and the why.
You can't do everything, nor should you. This template helps you figure out what is in and what is out of your project.
These are the do-or-die, must-meet requirements in order for the project to be considered a success. As such, they are continuously focused on by the project manager and core team.
Win Conditions address how success will be measured. How do you stack up when it comes to stakeholder satisfaction, your schedule, scope, quality, budget, ROI and team satisfaction? This template helps you rank priorities, and provides areas for metrics and descriptions.
The Risk Management Grid is a technique to identify potential risk events that could impact one of more of the project’s Seven Win Conditions. Importantly, it also serves to decide how those events will be prevented or mitigated.
Learn From Others
Most of us work on projects where we know the end date or the budget--or both. But there is a category of projects where we might not know either: emergent projects. Emergent projects are change projects such as your agile transition or any other project that you have no control over. Can you apply agile to those projects? Yes. Carefully.
Project teams quite often assume that the product manager is a true partner--and when a project is under scrutiny or stress, the product manager can transform into a very tough adversary and oftentimes a combative stakeholder. Put yourself in a product manager’s shoes for a change! Let’s explore a couple of myths about product managers that should hopefully spark a new level of collaboration and success…
Being nice is not a courtesy or even a basis for competitive advantage anymore. In today’s connected workplace with a less loyal and more mobile workforce, the economics of compassion are very real. See what smart companies are doing to recruit and retain the best talent.
Every aspect of product development can be done better or worse. That includes being a team player, writing code, communicating requirements, testing functionality...you name it. But how do you ensure that people do the best thing? And, can you even do that? That is, can you somehow force good practice? And what can you expect to happen by doing so?
It is a practical approach to understanding why decisions are so complex and what can be done about it. In order to create the combination between top-down problem decisions (waterfall-like approaches) and local problem decisions (agile-project approach), here are three practical guidelines.
...or, how a picture can divert 1,000 eyes. Pictures are cool. They aid discussion and unite comprehension. They also allow us to avoid having to read volumes of text. As such, they are the convenience food of project management. Easy to consume, but are they nutritious?
Should an agile team begin with requirements documented as use cases or user stories? Proponents from both sides of the debate make good arguments, leading to confusion for many who are just getting started with agile practices.
|A.||Using company time and resources to create a prototype wastes money and delays the actual completion of a shippable or deployable product or software. Listen to your manager. She is in that position because she knows more than you do.|
|B.||Managers do not always “hear” unless you speak in their own language and frame practices from the “What’s in it for me?” point of view. Find a good non-software example with budget numbers she can relate to and then translate this to substantiate why you think prototyping is almost mandatory in your situation.|
|C.||If you are not allowed to use prototypes when they are clearly called for, work with your team to slow down the velocity of your output. When asked by the product owner or external customer the reason for the delay, point the finger at your manager.|
|D.||Explain to your manager that she does not know how to develop software. Convey that a firm part of every Scrum cycle is to develop a prototype before moving on to do other user stories in the product backlog.|
With over half of companies using a blended agile and waterfall approach to development, it’s critical to be aware of how an agile approach affects planning and alignment with the overall business strategy. Here are the most common challenges in enterprise agile development--and some tips for how smart companies are navigating the new landscape.
Why is team ownership important? It is essential to agile team success because individuals thrive on ownership. With ownership, you have a stake in the game and push to find the best solution. The difficulty is that most corporate cultures have command-and-control leaders. Here is some help...
Ask a Question
|Mark All Read|