Chair of Software Engineering for Business Information Systems (sebis) Faculty of Informatics Technische Universität München wwwmatthes.in.tum.de Identifying recurring Challenges and Best Practices of Agile Coaches and Scrum Masters and Documenting them as a part of a Large-Scale Agile Development Pattern Language Nina-Mareike Harders, 11.01.2019, Kick-Off Presentation Master’s Thesis
17
Embed
Identifying recurring Challenges and Best Practices of ...€¦ · Identifying recurring Challenges and Best Practices of Agile Coaches and Scrum Masters and Documenting them as a
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Chair of Software Engineering for Business Information Systems (sebis) Faculty of InformaticsTechnische Universität Münchenwwwmatthes.in.tum.de
Identifying recurring Challenges and Best Practices of Agile Coaches and Scrum Masters and Documenting them as a part of a Large-Scale Agile Development Pattern LanguageNina-Mareike Harders, 11.01.2019, Kick-Off Presentation Master’s Thesis
… promises better products and higher customer satisfaction by continuous delivery and active customer involvement, deals better with changing requirements [5]
AGILE
Existing research at sebis found 14 Stakeholders having 79 challenges [3]
RESEARCH
Companies are inspired by the success of agile methods for small, co-located teams and apply them to large-scale projects [1,3]
LARGE-SCALE
… provide a structured solution to a recurring problem [4]
PATTERNS
… arise on different levels for different stakeholders, making it hard to obtain success at large-scale agile development [1,2,3]
CHALLENGES
… guides the user through the patterns based on his characteristics
Agile Coach [7] Scrum Master [6]• not part of the development team• create a productive, self-organized, agile team• works with existing teams• supports, gives feedback, trains• create mindsets and methods
• part of the development team• enable development process• promote agile values and practices• manage meetings• remove impediments
• Dealing with doubts in people about changes• Dealing with incorrect practices of agile development• Dealing with black and white mindsets• Dealing with closed mindedness• Establishing a common understanding of agile thinking and
practices• Encouraging development teams to talk about tasks and
impediments• Building an effective coaching model
• Coordinating geographically distributed agile teams• Facilitating agile teams to participate at cross-shore meetings• Synchronizing working hours of cross-shore agile teams • Dealing with lacking team cohesion at different locations• Building trust of stakeholders in agile practices• Establishing a culture of continuous improvement• Rearranging physical spaces• Dealing with higher-level management interferences• Dealing with cultural differences between cross-shore agile teams• Encouraging development teams to talk about tasks and
impediments• Synchronizing sprints in the large-scale agile development
[1] Dingsøyr, T., & Moe, N. B. (2014). Towards Principles of Large-Scale Agile Development. In Agile Methods. Large-Scale Development, Refactoring, Testing, and Estimation (Vol. 199, pp. 1–8). Cham: Springer International Publishing. http://doi.org/10.1007/978-3-319-14358-3_1[2] Challenges and success factors for large-scale agile transformations: A systematic literature review. (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review. Journal of Systems and Software, 119, 87–108. http://doi.org/10.1016/j.jss.2016.06.013[3] Uludag, Ömer & Kleehaus, Martin & Caprano, Christoph & Matthes, Florian. (2018). Identifying and Structuring Challenges in Large-Scale Agile Development Based on a Structured Literature Review. 10.1109/EDOC.2018.00032. [4] Jan vom Brocke, Peter Fettke, Peter Loos, Stefan Junginger, Christoph Moser, Wolfgang Keller, Florian Matthes, Alexander Ernst, & Winter, R. (2009). Patterns in der Wirtschaftsinformatik. Wirtschaftsinformatik, 51(6), 535–542. http://doi.org/10.1007/s11576-009-0195-5[5] Dingsøyr, T., Nerur, S. P., Balijepally, V., & Moe, N. B. (2012). A decade of agile methodologies - Towards explaining agile software development. Journal of Systems and Software, 85(6), 1213–1221. http://doi.org/10.1016/j.jss.2012.02.033[6] Bass, J. M. (n.d.). Scrum Master Activities: Process Tailoring in Large Enterprise Projects (pp. 6–15). Presented at the 2014 IEEE 9th International Conference on Global Software Engineering (ICGSE), IEEE. http://doi.org/10.1109/ICGSE.2014.24[7] Davies, R., & Sedley, L. (2009). Agile coaching. Pragmatic Bookshelf.[8] Lucrédio, Daniel & Santana De Almeida, Eduardo & Alvaro, Alexandre & Garcia, Vinicius & Kessler Piveta, Eduardo. (2004). Student's PLoP Guide: A Pattern Family to Guide Computer Science Students during PLoPConferences.