Scrum Team Structures

  • McKenna D
N/ACitations
Citations of this article
6Readers
Mendeley users who have this article in their library.
Get full text

Abstract

I find that most people don't think of their day-to-day work in the terms of operating within the structure of a team, let alone becoming a high-performing team. Before Agile, the workplace was a very competitive place, where everybody focused on themselves. People worked isolated in cubicles and only came together for status meetings where management looked for whom to chastise because they were behind in their work. Now the focus needs to be on the team and collaboration. Those impacted by decisions make those decisions. Failure is looked at as an opportunity to grow, not to point fingers and shift blame. Information and knowledge is freely shared, and quality is emphasized over meeting a specific date.

Cite

CITATION STYLE

APA

McKenna, D. (2016). Scrum Team Structures. In The Art of Scrum (pp. 55–61). Apress. https://doi.org/10.1007/978-1-4842-2277-5_4

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free