If we are limited by the triple constraint, how do we as project managers lead with agility and embrace change? If projects are all about needs and values, then project management should be the tools and techniques to achieve this value. Is it time to redefine project management? Should we move away from the iron triangle to the value triangle?
Connect In Person
Advance your BA skills. Earn PDUs and more—all for free. Don’t miss the most popular Business Analysis event of the year! Over 13,000 attend. Registration is FREE. We’re sharing career journeys and talking about the hottest BA and agile BA topics. Register now to attend the only event designed with your future in mind to help you get ahead.
Is Your Agile Transformation Set up to Fail? Find out at the PMI® Organizational Agility Conference 2016, FREE and Exclusive for PMI Members. We know there are barriers that slow your organization’s ability to be agile: failed agile transformations, complex organizational processes, team dynamics and the uncertain role of the PMO in an agile environment (just to name a few). Attend the PMI Organizational Agility Conference 2016 to get help breaking down these barriers. It’s free for PMI Members.
Overwhelmed by how technology is transforming project management? Looking to increase your productivity and learn new tech tools but don't know where to begin? No matter what your focus—medical, manufacturing, product design or otherwise—this virtual day of learning will deliver years of enduring value, with exclusive insights on how project managers are using new technologies.
The goal of this session is to dig deeper into practical ways to start shifting to Stable Teams while sharing years of experience from the real world in making this vision a reality.
In this webinar, we’ll go through what the issues are when transitioning to an Agile mindset, how they present themselves and what you can do as a Project Manager to think ‘more agile’ in your projects whilst accepting and learning along the way.
This is the final session in our six-part How to Be a Project Hero series. In this session we will discuss how to bring all the pieces together in a LEAN plan and share some techniques on tracking against that plan.
The journey to Adaptive and Servant Leadership is a long one, it doesn't happen over night and it takes conscious effort to get there. I want to share some of the best tips we've learned from the real world on how to navigate this journey and help others do the same.
In case you actually read this description, the beginning of the blog is about preparing for the PMP exam. It then evolved into maintaining my credential. After taking a break for a few years, I'm back and will be blogging about project management, in general, and probably a bit of agile on a regular basis.
The Agility Series focuses on agile and agility across the organization not just in software and product development. Areas of agility that will be covered in blog posts will include: - Organizational Agility - Leadership Agility - Strategic Agility - Value Agility - Delivery Agility - Business Agility - Cultural Agility - Client Agility - Learning Agility
This blog is a conversation between the Agile Practice Guide Team and our PMI and Agile Alliance Communities to gain insight, support and collaboration around the creation of a usable and relevant body of work that supports transition to hybrid and agile in project work.
Save Time With Tools + Templates
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.
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.
Learn From Others
When companies move to an agile Software Development Lifecycle (SDLC), they often remove the processes and analysis of their waterfall SDLC because, as the Agile Manifesto puts it, “They value individual and interactions over processes and tools.” Some of the rigor should be removed – waterfall processes can get bogged down with gates and sign-offs. However, caution must be exercised to not go too far against processes and analysis and rely just upon backlogs and user stories. Requirements and the analysis that leads to those requirements are just as essential in an agile project as they are in a waterfall project. The difference lies in how much requirements analysis is completed and the timing of it.
|A.||There is a reason for the “chalk and cheese” expression. When you mix them you either forfeit a beautiful drawing or you miss a delightful appetizer. While multiple teams can work successfully on a common deliverable, it is vital that all teams are using exactly the same approach.|
|B.||By now, 15 years after the meeting to create the Agile Manifesto, all teams should be aware that in today’s marketplace the only way to keep your organization competitive and protect your own job is to work in an exclusively agile environment. Most of the newsworthy business closings or serious curtailing of products are in industries that refuse to go agile.|
|C.||It is not only possible for an agile team and a traditional team to work together successfully, it’s probably going to become the norm for more and more projects in the future. The secret it to understand where you can sync your work and where you need to use the parts of your preferred approach freely in order to have the best end outcomes.|
|D.||While agile works situationally in software, the traditional methodology espoused by A Guide to the Project Management Body of Knowledge (PMBOK® Guide) has the advantage of a 55-year history. The knowledge amassed within that length of trial and error makes waterfall the preferred approach for all industries that want to make projects successful.|
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog. This is the last paper in this series and covers decision models, which include both decision trees and decision tables.
Is your organization undermining the benefits of Scrum without even knowing it? Scrum is a simple agile framework that can be difficult to implement. Here the author looks at the seven most commonly missed or abused rules of Scrum.
Organizations who are now embarking on agile adoption are feeling pressure to “catch up” with their competitors. But when “late adopters” of agile try to make up for lost time, it can cause problems.
Testing at the end of a development cycle is a common practice in traditional approaches. Unfortunately, it becomes an obstacle on your path to agility, slowing down your ability to deploy to production faster. Let’s take a look at what goes on in this testing phase, some potential causes and ideas for getting unstuck.
In this article, we will review the contentious topic of how the BA role varies and overlaps with the product owner role. We cover the similarities and differences, including danger signs (such as the “BA as PO Go-Between”) and positive patterns (such as the “BA as PO Supporter”).
This series provides valuable information for the product owner community to use additional good practices in their projects. In each edition of this series, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog. This installment covers state models, which include both state diagrams and state tables.
Iterative and incremental methods can be used outside software development. Here’s a challenge that arose in one small-town Shakespeare festival--and the “agile” approach used to meet it.
Have you been thinking about getting your PMI Agile Certified Practitioner (PMI-ACP)® credential but are put off by the agile experience requirement? Fear not, you might have the experience you need even if you have not been working on a pure agile project. This article explores the prerequisites elements and explains what you need to qualify.
Agile self-organized teams come up with a wider variety of options and better solutions than you ever could alone. And there are a number of things you can do as an agile manager to help create the work environment for a self-organized team, be it co-located or distributed.
If you adopt the agile approach, it will affect every aspect of your work. Learning it will be challenging for you, your team and your organization. The learning process will take months or even years; during this time, you still need to produce results. After 20 years of agile’s existence, do we know of a reliable, effective way of learning it?
It took this practitioner a while to find her footing as both a project manager and ScrumMaster. Here, she shares lessons learned in a large, corporate environment in which agile is considered "new."
Following installments on the other four stated Scrum values (courage, focus, openness and commitment), this concluding entry focuses on respect. It offers techniques to scrutinize agile project management frameworks based on values, principles and practices.
Agile approaches promote development teams comprised of generalizing specialists and seem to ignore the BA role. This begs the question: Do BAs have a role on agile projects? And if so, how do their functions change? This article examines their new role, what changes and what stays the same.
To rise above the competition requires tenacity, veracity and intangibles that organizations need to respect, comprehend and practice. Business success is cultivated through sound project management practices, which include business rhythm, organizational intangibles, organizational development, project production, project delivery and a project management team. These key ingredients, when working together, guarantee project success.
Ask a Question