Situational Awareness for Project Managers

March 20, 2017 10:54 PM | COMMENTS (0) | CATEGORIES: Project Management

Wanda Curlee and Cornelius Fichtner

Every project manager needs to master situational awareness. That is because no two projects are perfectly alike. What worked last time may have to be tweaked next time. Even worse, what may have worked just yesterday may have to be tweaked today!

(Click to download MP3...)

This interview about situational awareness with Wanda Curlee was recorded at the Project Management Institute (PMI)® Global Congress 2016 in San Diego, California. It was co-written and co-presented with Marie Sterling. Wanda and I discuss their presentation and white paper Situational Awareness. Do you have the Emotional Intelligence for it?. Here is the abstract:

This paper explores the relationship of situational awareness and emotional intelligence of portfolio, program, and project leadership. Included in the paper is an introduction to situational awareness, emotional intelligence, SAGAT, recommendations and details about the workshop exercise. Situational awareness plays a critical role in effective decision making, and more so in complex and challenging portfolio, program and project management environments. Emotional Intelligence (EI) is the study of how in tune a person is with his or her own emotions and the ability to understand emotions of those around himself or herself. Through the use of a live training simulation, an individual’s level of situational awareness and their emotional intelligence will be determined.

(This interview was originally published on The Project Management Podcast.)


Project Failure Is Not An Option

March 15, 2017 03:38 AM | COMMENTS (0) | CATEGORIES: Project Management

Kristy Tan Neckowicz, Connie Inman and Cornelius Fichtner

At some point in their career, every project manager has to deal with troubled projects.

(Click to download MP3...)

This interview about project recovery with Kristy Tan Neckowicz and Connie Inman was recorded at the Project Management Institute (PMI)® Global Congress 2016 in San Diego, California. We discuss their presentation and white paper Recognize Warning Signs and Rescue Your Troubled Projects. Here are the abstract and summary:

Abstract: Come to this session to hear real stories of troubled projects and recovery journeys from two seasoned project management professionals. You will learn to recognize common warning signs of troubled projects, approaches to right-sizing your project management processes, and applications of stakeholder management lessons for project success.

Summary: The common theme across the case studies is a focused spirit of continuous improvement to rescue troubled projects. Although projects are temporary in nature, project management processes are always evolving.

It is tempting to move on to the next project when a troubled project has been placed safely back on track. However, you will have more assurance of the project manager’s future success by conducting a lessons learned evaluation focused on the practice of project management before claiming victory.

By sharing the warning signs, right-sizing approach, and lessons learned from these case studies, we hope you will leverage our experience to keep your next project “on track” to successful delivery.

(This interview was originally published on The Project Management Podcast.)


Top Five Warning Signs that Agile Isn't Working

March 08, 2017 12:21 AM | COMMENTS (1) | CATEGORIES: Agile

NK Shrivastava

This interview about why Agile might be failing in your organization with NK Shrivastava was recorded at the Project Management Institute (PMI)® Global Congress 2016 in San Diego, California. We discuss his presentation and white paper Top Five Warning Signs That Agile is Not Working for You. Here are the abstract and conclusion:

(Click to download MP3...)

Abstract: There are good possibilities of success when adopting an agile approach in an organization, but five symptoms in particular serve as warning signs that the organization’s agile transformation is not working well.

The five warning signs include: (a) no signs of value delivery for over 3 months, (b) teams resisting customer changes, (c) teams “waterfalling” sprints, (d) customers foregoing involvement in development and testing, and (e) lack of visibility for agile in the organization. Potential solutions for these problems are also described in this paper. Many organizations can solve these problems internally, but sometimes an external resource such as a change agent or an agile coach is needed. By addressing these issues, organizations can increase the chances of a successful agile transformation.

Conclusion: Agile doesn’t work by itself. Organizations that implement agile with minimal team support and expect it to work perfectly “out of the box” will likely be disappointed. Successful agile adoption depends on factors at the organization and team levels. Organizations need the right mindset, a strong commitment, a culture conducive to implement agile, and the ability to secure resources and outside help as needed. Teams need the training, skills, and empowerment to absorb and implement agile principles. With these factors in place, organizations and teams should be able to build the foundation for agile success.

(This interview was originally published on The Project Management Podcast.)


Scaled Agile for The Enterprise

March 06, 2017 12:37 AM | COMMENTS (2) | CATEGORIES: Agile

Joy Beatty

We continue our look at the topic of scaled agile that we started in the previous episode, this time by looking at "agiLE" - Agile in the Large Enterprise.

(Click to download MP3...)

This interview about Scaling Agile with Joy Beatty, PMI-PBA was recorded at the Project Management Institute (PMI)® Global Congress 2016 in San Diego, California. We discuss her presentation and white paper Making "agiLE" Work: Agile in the Large Enterprise. Here are the abstract and final thoughts:

Abstract: Almost all large enterprises are making some transition to agile practices. There are many approaches to scale agile in the large enterprise, and we’ll give an overview of the most common scaled approaches and their limitations. This paper also discusses the most common challenges our customers’ teams are facing when scaling agile and provides suggestions to overcome those challenges.

Final Thoughts: This sounds like a daunting task—to transition to agile approaches in a large organization. However, with solid collaboration and communication, it’s absolutely doable. Teams will constantly be collaborating through elicitation, answering questions, and testing the actual product. Business analysts have a critical role to play in keeping the collaboration running smoothly, including helping to facilitate backlog grooming and elaboration, participating in planning in sprints, working with interfacing teams to identify dependencies, and serving as a product owner proxy on any teams as needed. Likewise, project and program managers can act as advisors about appropriate levels of process, help guide projects toward common goals, and ensure a focus on prioritization based on business needs. Instead of instilling a hierarchical control between PMO and product owner, in agiLE the PMO and product owner work together to achieve the objective. The real goal for agiLE teams is self-organization and creativity, while still contributing as a part of a large organization

(This interview was originally published on The Project Management Podcast.)


Scaled Agile

February 27, 2017 04:12 AM | COMMENTS (0) | CATEGORIES: Agile

Andrew Burns

Agile began with the promise to make smaller project teams more able to react to ever changing customer requirements. But what if your project is big? I mean really, really big. Can we have scaled agile?

(Click to download MP3...)

This interview about Scaling Agile with Andrew Burns, PMI-ACP, PMP, was recorded at the Project Management Institute (PMI)® Global Congress 2016 in San Diego, California. We discuss his paper and presentation Dragon Scales: 50 Teams Scrumming -- Implementing Adaptive Project Management Practices at Scale. Here is the abstract:

Product portfolios can easily scale to 50 teams or more in meeting large organizations’ needs. Large portfolios with strong foundations are derived through values-based leadership. The technique links corporate and individual values to scientific principles. Scientific principles inform us that change is constant and therefore adaptation defines good practices. Values-based leadership’s agile practices take root, thrive, and adapt at the pace of business change.

The three-hundred software engineers considered herein innovated within a portfolio of 18,000 colleagues. Their agile, adaptive product development practices continue to evolve from plan-driven provenance. Leveraging agile practices at the portfolio, program, and project level continually unleashes innovation, quality, and throughput of value. Though contextualized in terms of software product development in the 2010s with Scrum, the message of innovation through values-based adoption of scientific principles is timeless and framework unallied. Implementation of practices observant of values and principles endures as a way to deliver the best products regardless of toolset.

(This interview was originally published on The Project Management Podcast.)