Project Management

Please login or join to subscribe to this thread

How do you manage the perception that Agile Project Management means no planning

linkedin twitter facebook   Agile   Communications Management   Disciplined Agile  
avatar
Julio Ramos Chief Information Security Officer| AFTAC Merritt Island, FL, United States
I must continually remind Project Managers and team members that Agile does not mean no planning.  The prevailing perception is that Agile mean go do and we figure it out later
Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Scrum does lend itself to learning as you go, and there are times when that can be the appropriate approach. Do you have a Product Owner, or somebody (not the project manager or a project team member) identifying and prioritizing requirements/stories?

Are you just dealing with the PM and Team's perception, or is there someone else in a leadership position driving their behavior?
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
I've run into this mindset before, and it was usually held by upper management in addition to others lower down the ladder.
Do you know the type of Agile training people in your organization received? It's possible the expectations of each role weren't well-explained. If so, you could create a short presentation to rectify that.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Julio -

I'd suggest searching for Scott Ambler's great blog series in this community on the perils of over and under planning as they should provide some guidance on how to educate your stakeholders who are holding these views.

Kiron
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Julio, stakeholders need some education as this misconception is very common. Being agile definitely doesn't mean no planning and instead it means planning in advance just enough.
Start with the end in mind !. How much planning is required depends on the lifecycle the team choose to deliver an increment/value for the type of product/services ? is it going to be Continuous delivery or iterations or stages/milestones ? If you refer this link for eg., https://www.pmi.org/disciplined-agile/lifecycle/cdlean-lifecycle , it promotes the team to pull work based on the available capacity. Does your team and Project managers having perception like this ? I would say you need to first check where that perception comes from.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Just take a look to this: https://agilemanifesto.org/history.html
avatar
Jim Morgan Durham, NC, United States
I call up the front page of the Agile Manifesto, and point to the line under the four "over" statements: "That is, while there is value in the items on the right, we value the items on the left more." Agile teams still have processes, tools, documentation, contracts, and plans. But each embraces change rather than resisting it.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If a man does only what is required of him, he is a slave. If a man does more than is required of him, he is a free man."

- Chinese Proverb

ADVERTISEMENT

Sponsors