Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library


A Partner Is Good to Have, but Difficult to Be

  • April 2015
  • By David Kane (Santeon Group), Dave Dikel (InSysCo)
  • This workshop illustrates the importance of partnering skills in the context of software architecture for increasing stakeholders' engagement and trust.
  • Publisher: Software Engineering Institute
  • This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.
  • Abstract

    This workshop will help participants build partnering skills and avoid pitfalls through games, examples, and discussion and show how these skills can produce better results for the architecture team and its customers. Architecture efforts can be sidelined without the engagement and trust of software developers and project managers, yet architects do not always see collaboration and service as part of their role. Lack of collaboration and service on the part of an architect can result in an architect's

    • uncertainty about whether and how well products are being used or delivering value
    • products and guidance being "worked around" rather than incorporated
    • rigid and less-than-effective use of stakeholder-related architecture practices

    We will illustrate the importance of partnering in the context of architecture. We define partnering as "the extent to which architecture stakeholders maintain clear, cooperative roles and maximize the value that they deliver and receive." We will also share and facilitate a discussion using hands-on ideas and examples of how to build on existing partner relationships to increase engagement and trust.

  • Slides

Part of a Collection

SATURN 2015 Presentations