Summary of “Managing Projects: A Team-Based Approach” by Karen Brown and Nancy Hyer (2013)

Summary of

Operations and Supply Chain ManagementProject Management

Introduction

Managing Projects: A Team-Based Approach by Karen Brown and Nancy Hyer offers a fresh perspective on project management by emphasizing the importance of teamwork. The authors argue that while traditional project management focuses on schedules, budgets, and scope, successful project delivery relies heavily on effective team dynamics and collaboration. This summary covers the key points of the book, organized into different sections that highlight major themes, useful actions, and real-world examples provided by the authors.

Section 1: The Foundation of Team-Based Project Management

Key Points

  1. Importance of Team Creation:
  2. Brown and Hyer stress the importance of building a cohesive project team from the outset. They recount examples showing that teams which are thoughtfully assembled perform better.

  3. Defining Roles and Responsibilities:

  4. Clearly defined roles help prevent misunderstandings and ensure that all team members know their tasks. The authors provide a framework for establishing roles within a project team.

Action Items

  • Team Selection: Select team members based on both technical skills and interpersonal compatibility. A good blend of these qualities fosters a productive work environment.
  • Role Clarification: Utilize tools like RACI charts (Responsible, Accountable, Consulted, Informed) to delineate roles and responsibilities. This ensures everyone is aware of their specific duties and prevents overlap.

Example

The authors illustrate their points using the case of a mid-sized tech company that restructured its project teams by clearly defining roles. The improvement in project delivery times and team morale was significant, underscoring the importance of clear role assignments.

Section 2: Communication and Collaboration

Key Points

  1. Effective Communication Practices:
  2. Successful projects hinge on clear, concise, and regular communication among team members. The authors focus on the importance of open channels of communication to avoid misalignment.

  3. Collaborative Tools and Techniques:

  4. Various tools (like project management software, collaborative platforms, etc.) can facilitate better teamwork. Teams that effectively use these tools tend to have higher success rates.

Action Items

  • Regular Meetings: Schedule regular status meetings to keep everyone aligned. Daily stand-ups or weekly check-ins can be very effective.
  • Utilize Technology: Introduce collaboration tools such as Slack, Trello, or Microsoft Teams to streamline communication and improve collaboration.

Example

Brown and Hyer showcase a marketing team’s transition to using Slack and Asana to manage projects. The immediate improvement in communication flow and project tracking significantly boosted their output.

Section 3: Managing Conflict and Building Consensus

Key Points

  1. Addressing Conflict Early:
  2. Conflict is inevitable in project teams, but how it is handled can make a huge difference. Early intervention and conflict resolution are crucial.

  3. Consensus Building:

  4. Reaching consensus is essential for team buy-in and project success. The authors discuss techniques for achieving consensus without compromising project goals.

Action Items

  • Conflict Resolution Training: Provide team members with training on conflict resolution techniques. This can include role-playing exercises and workshops.
  • Facilitation Techniques: Employ facilitated meetings to build consensus. Techniques such as the Delphi method or SWOT analysis can help align team perspectives.

Example

An example cited in the book involves a pharmaceutical company that implemented conflict resolution workshops. The team members learned to address issues constructively, preventing minor disagreements from escalating and ensuring smoother project execution.

Section 4: Planning and Execution

Key Points

  1. Detailed Project Planning:
  2. Comprehensive planning at the outset leads to smoother execution. This includes defining project scope, timelines, and resource allocation.

  3. Agile Approaches:

  4. The authors promote the use of Agile methodologies for certain projects, as they allow for flexibility and iterative progress.

Action Items

  • Work Breakdown Structure (WBS): Create a WBS to divide projects into manageable sections, outlining tasks and responsibilities clearly.
  • Adopt Agile Practices: For projects that demand flexibility, consider adopting an Agile approach, incorporating sprints, and regular retrospectives.

Example

Brown and Hyer describe a software development team that switched from a traditional waterfall model to Agile. The shift allowed for faster iteration and responsiveness to client feedback, leading to higher satisfaction rates.

Section 5: Monitoring and Controlling

Key Points

  1. Performance Monitoring:
  2. Consistent monitoring is necessary to ensure that the project stays on track. Key Performance Indicators (KPIs) and regular audits can help with this.

  3. Risk Management:

  4. Identifying potential risks and having mitigation strategies is vital for project success. The authors provide a framework for effective risk management.

Action Items

  • KPIs and Dashboards: Implement KPIs and dashboards to monitor project progress in real-time. This provides a clear visibility into project health.
  • Risk Assessment Workshops: Conduct risk assessment workshops at regular intervals to identify and mitigate potential risks.

Example

An example provided involves an automotive company that introduced monthly risk assessment sessions. By proactively addressing potential issues, they were able to avoid significant setbacks and complete the project on time.

Section 6: Closing the Project

Key Points

  1. Project Review and Closure:
  2. The closure phase is an opportunity to review what went well and what didn’t. It’s essential for capturing lessons learned and improving future projects.

  3. Celebrating Success:

  4. Celebrating team achievements helps build morale and can motivate team members for future projects. Recognizing contributions is a key factor in maintaining a positive team dynamic.

Action Items

  • Post-Project Reviews: Conduct detailed post-project reviews. Gather feedback from all team members and stakeholders to compile a comprehensive lessons learned document.
  • Recognition Programs: Implement a recognition program to celebrate team successes. This could be as simple as a team lunch or more formal awards.

Example

The book concludes with an example of a consulting firm that holds a “Post-Project Celebration” event after every major project. They review the project outcomes, discuss lessons learned, and celebrate successes, fostering a culture of continuous improvement and team recognition.

Conclusion

Managing Projects: A Team-Based Approach by Karen Brown and Nancy Hyer provides a comprehensive guide to executing projects through effective teamwork. By emphasizing the human factors involved in project management, the authors offer valuable insights into how to build, maintain, and lead successful project teams. While the traditional metrics of time, cost, and scope remain important, the focus on team dynamics offers a more holistic approach to achieving project success. Implementing the actionable advice and leveraging the real-world examples highlighted in this book can help project managers strengthen their teams and enhance project outcomes.

Operations and Supply Chain ManagementProject Management