Project Management

How does Agile differ from traditional PM practices?

Connect with Influencers

avatar
Phillip George RefineM Springfield, Mo, USA

avatar
Riam Chazbek President of PMI Lebanon Chapter - PMO Consultant| Ernst and Young Beirut, Lebanon

avatar
Ori Dvir Project Management Consultant| Self employed Tel Aviv, Israel

avatar
Lavanya Vijayaraghavan Passionate about Projects | Proud PMI Volunteer Bangalore, Karnataka, India

avatar
Mike Frenette
Community Champion
Manager, IT PMO| Halifax Water Halifax, Nova Scotia, Canada

avatar
Mirko Kleiner Thought Leader Lean-Agile Procurement • co-founder flowdays • Agile Coach | flowdays - THE agile cooperative! Switzerland

avatar
Mike Griffiths President| Leading Answers Canmore, Alberta, Canada

avatar
Ansley Anchors Marketing Coordinator| Afterburner Atlanta, Ga, USA

avatar
Torgeir Dingsoyr Chief Scientist / Adjunct professor| SINTEF Digital / Norwegian University of Science and Technology Trondheim, Norway

avatar
Antonio Nieto HBR Author | Director PMO | PMI Fellow & Past Chairman | Professor | Thinkers50 | Projects & Company Brussels, Belgium

Pages: 1 2 3 4 <prev| next>

Does Risk Management have a place in an Agile Lifecycle

by Greg Smith, Donna Reed
January 27, 2011 | 45:11 | Views: 1,591 | PDUs: 1.00 | Rating: 4.14 / 5

We often have questions about relating traditional PM practices to Agile practices. This is especially true in the area of risk. In this one hour webinar, Greg will cover traditional risk management techniques and contrast them to the Agile risk management practices. Areas covered include BURP (Big Upfront Risk Planning), daily risk management, and team involvement in risk identification. You will learn how to use traditional risk management in harmony with an Agile lifecycle and how to perform risk management at a level that minimizes waste and over-planning.

Beyond Scope, Schedule, and Cost: Rethinking Performance

by Jim Highsmith
March 15, 2011 | 45:25 | Views: 3,134 | PDUs: 1.00 | Rating: 3.99 / 5

Agile teams are asked to be agile, flexible, and adaptive, but then are told to conform to planned scope, schedule, and cost goals. They are asked to adapt, but inside a very small box. If we are to scale agility to large projects and bring agile values to organizations, then we must change performance measures. To mirror the Agile Manifesto, it's not that scope, schedule, and cost are unimportant, but that value and quality are more important. This talk explores the necessity for and the rationale behind moving to this new set of agile performance measures

Transitioning to Agile: A PM's Experiences

by Ravishankar Srinivasan

This writer's organization was involved in software development--and was a strong matrix organization with the functional teams organized according to technology domains. Project managers were responsible for end-to-end delivery. But to deal with fast-moving competition and a rapidly changing business environment, the management decided to adopt agile--and Scrum was the chosen methodology.

PMBOK Supplementing Agile Processes

by Saumyabehura

While agile processes focus on time-to-market product delivery, continuous stakeholder engagement, embracing the changes even at a late stage and most importantly developing a highly efficient team, these processes are, in fact, abstract in nature. There are several aspects left open to the agile teams. So why can't we take advantage of A Guide to the Project Management Body of Knowledge (PMBOK Guide) to fill in these aspects?

Confessions of an Agile Project Manager: 2 Cents

by Troy Bitter

Some traditional project managers transition to servant leadership easily. Others work on it. As this practitioner coaches project managers to become servant leaders, he teaches a simple technique...

Agile Implementation of Outsourced Projects

by Chandramukhi Radhakrishnan

While it is imperative in this competitive IT industry to comply with customer demands, it is also equally important to educate and negotiate with the customer on the suitability of the model for the project. Typically, a high-bred model combining waterfall, iterative and agile seems to be more apt for outsourced IT projects with diverse teams boyj onshore and offshore.

Did You Say a 'Constraint Diamond'?

by Asha Subramanian

It demands a shift in focus and emphasis to support the shift in approach from the traditional sequential waterfall to the newer incremental agile.

From Problem Space to Solution Space: The Flexibility of Agile Rituals

by Amandeep Bhatia

Most of the rituals such as Daily Stand-ups and retrospective meetings give us a nice platform to carry forward an approach of thinking in terms of solutions and engage with the customer or distributed teams more efficiently. This practitioner started sharing this practice with his teams and calls it “moving from the problem space to solution space”.

We Iterate...So We're Agile?

by Illya Pavlichenko

Working with iterations does not automatically make you an agile team. It doesn't even necessarily mean that you are using iterative development. Paradoxically, it is possible to be agile without use of iterations. Let’s get into details...

Thinking and Acting as a Team on Your Agile Projects

by Mark Layton

Agile project team members will succeed or fail as a single unit, not individually. In an agile environment, the entire project team should be aligned in its commitment to the goal, its ownership of the scope of work and its acknowledgment of the time available to achieve that commitment.

A Better Burndown for More Accurate Sprint Planning

by Todd Bookless

One of the secrets of a practitioner's success is that I he has varied from the traditional burndown chart and sprint estimation suggestions that are taught when a person learns about Scrum. If you have had issues with making accurate burndown charts that reliably tell you when your sprint will finish, then perhaps his suggestions can help.

EXPAND YOUR KNOWLEDGE

ADVERTISEMENTS
ADVERTISEMENT

Sponsors