Agile methods recognize the increased need for communication and provide a variety of tools and checkpoints to help avoid the classic project mistakes of mismatched expectations and confusion. In the absence of a visible physical product to point at and measure, we need to be constantly confirming understandings and aligning ideas against increments of the final solution.
The agile approach needs to be understood thoroughly before it is introduced to a company. This explanation will give leadership the information they need for deciding if agile project execution is right for their organization by discussing key points including core framework, high-level benefits, and risks in the project-based environment.
by Sam Falcone, MSW, MBA, PMP, CSM, Lisa Binckes, M.A., Co-Sponsor
The General Services Administration’s (GSA’s) Public Buildings Service (PBS) needed better knowledge management (KM) approaches for supporting their building maintenance, leasing, construction, and renovation projects delivered annually across the United States. A national KM team, utilizing a rapid piloting approach, customized preexisting/prepaid software tools to quickly meet their information needs. Read the case study for details about lessons learned and critical success factors.
Agile adoption outside of software is nothing new--it dates back very close to the origin of today’s agile methods, predating the term “agile”. However, what is new and noteworthy is the rate and scale of non-software agile adoption being witnessed today. Now--as more companies than ever are exposed to agile methods in their IT practices--these methods are being employed beyond the regular IT domain.
Agile projects are optimized for different constraints than traditional ones. To truly understand how to design a performance measurement system for agile PM, we need to dig a little deeper into the value system underlying agile methods.
This article shares a real-time learning experience in agile software development methodology during project execution. The author offers insights into project challenges, lessons learned and success realized, referencing the Manifesto for Agile Software Development and agile principles.
by Susan Irwin, MBA, PhD, PMI-ACP, PMI-SP, PMP, PgMP, PfMP
Project managers need leadership skills—specifically emotional intelligence (EI)—to augment technical expertise. But agile thinking, leadership and EI skills are just one facet of project success. Businesses need to invest in project management processes that are agile to respond to the changing needs of the organization.
This article shares how practicing aikido—a spiritual martial art founded in Japan—provides a project manager valuable leadership lessons in his or her daily struggle to achieve desired objectives.
Ending the project is about more than just post-mortems and parties (don't worry, you can still have those, too!). Here we explore why we want to ensure that the project adds to the overall organizational knowledge--and how formal closure to all of the project elements must leave no confusion, gaps or misinterpretation.
Look! Up in the sky! It's a bird! It's a plane! It's a...checklist?! You may not give them their due, but checklists are far more important and vital than you can imagine. Here, we take a look at the history and value of one of the most overlooked tools in the project manager's arsenal.