Chair of Software Engineering for Business Information Systems (sebis) Faculty of Informatics Technische Universität München wwwmatthes.in.tum.de Survey and Analysis of Scaling Agile Practices for an Agile IT Organization Binnur Karabacak, Bachelor Thesis Final Presentation, 31.07.2017, Munich
33
Embed
Survey and Analysis of Scaled Agile Frameworks for an Agile … · ... Product Owner, Scrum Master, Development team, Area Product Owner Events Iteration ... Inspect and Adapt, Iteration
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 Informatics
Technische Universität München
wwwmatthes.in.tum.de
Survey and Analysis of Scaling Agile Practices
for an Agile IT Organization Binnur Karabacak, Bachelor Thesis Final Presentation, 31.07.2017, Munich
[1] VersionOne Inc. (2017). the 11th annual State of Agile Report. accessed: 2017-07-27.
[2] J. Vom Brocke, A. Simons, B. Niehaves, K. Riemer, R. Plattfaut, and A. Cleven. (2009), “Reconstructing the giant: On the importance of rigour in documenting the literature search process,” in ECIS, vol. 9, pp.
2206–2217.
[3] Alqudah, M.; Razali, R. (2016). A Review of Scaling Agile Methods in Large Software Development. International Journal on Advanced Science Engineering Information Technology, 6 (6), 828-837.
[4] Dolman, R.; Spearman, S. (2014). Links. Retrieved from Agile Scaling: http://www.agilescaling.org/links.html. accessed: 2017-07-27.
[5] A. Pant, “Agile methodology: Implementing the best scaled agile framework for faster and better business results,” Tavant Technologies, Tech. Rep., 2016.
[6] S. V. D. Z. Mike West, Nathan Wilson, “Market guide for enterprise agile frameworks,” Gartner, Tech. Rep., 06 2016.
[7] Kapadia, M.: Introduction to Enterprise Agile Frameworks, Salt Lake City, Utah 2014.
[8] Uludağ, Ö.; Kleehaus, M.; Xu, X.; Matthes, F.: Investigating the Role of Architects in Scaled Agile Frameworks, 21th Conference on Enterprise Distributed Object Computing (EDOC), Québec City, Canada 2017.
[9] “Safe® 4.0 for lean software and systems engineering”, http://scaledagileframework.com/, accessed: 2017-07-27.
[10] LeSS Framework, https://less.works/ , accessed: 2017-07-27.
[11] Kaczmarek, C. (2016). Organisation in einer Digitalen Zeit: Ein Buch für die Gestaltung von reaktionsfähigen und schlanken Organisationen mit Hilfe von skalierten Agile & Lean Mustern. Darmstadt: Wibas GmbH
Product Backlog defines all of the work to be done on the product
Sprint Backlog work that the team will need to do for completing the selected Product Backlog Items
Event
Sprint in each sprint, a potentially shippable product increment results; duration: 2-4 weeks
Sprint Planning one all of the teams come together and decide which team will work on which items
Sprint Planning two separate meeting per team where each team creates the plan for getting the items to ‘done’ during the Sprint
Daily Scrum
daily meeting per team, during which each team member tells, what he did yesterday, what he will work on today, and possible impediments
Sprint Review
inspect-adapt point at the end of the Sprint; customers and stakeholders examine what the teams built during the Sprint and discuss changes and new ideas
Sprint Retrospective
at the end of the sprint; each team has ist own retrospective; create a plan for improvements to be enacted during the next Sprint
Overall retrospective discussion of cross-team, organizational, and systemic problems within the organization
Roles
Scrum master responsible for one up to three teams
product owner
one product owner for all teams; responsible for maximizing the value of the product and the work of the Development Team; at scale the focus is rather on keeping an overview and ensuring the maximum return on investment (ROI) in the product
development team Source: based on LeSS
Backup: Definition of artifacts, events and roles of SAFe
servant leaders and coaches for an Agile team; help educate the team in Scrum, eXtreme Programming, Kanban and SAFe, ensuring that the agreed Agile process is being followed
Product Owner
content authority for the team level; responsible for the team backlog, prioritizing and accepting stories, and representing the customer to the Agile team
Agile Team member
Program level
Release Train Engineer
coach for the ART; facilitate the major events and processes, and assist the teams in delivering value
System architect/engineer
represents an individual or small team that defines a common technical and architectural vision for the Solution under development
Product Management
authority for the Program Backlog; responsible for identifying customer needs, prioritizing features and developing the program Vision and Roadmap
Business Owner
small group of stakeholders who have the primary business and technical responsibility for governance, compliance, and Return on Investment for a Solution developed by an Agile Release Train
Source: based on SAFe 2016
Backup: Definition of artifacts, events and roles of SAFe
Value stream engineer similar role as RTE; facilitatin and guiding the work of all ARTs and suppliers
Solution management
content authority for the Solution Backlog; work with Customers to understand their needs, create the Solution vision and Roadmap, define requirements, and guide work through the Solution Kanban
Solution architect/engineer help align the Solution Train and the Agile Release Train to a common technological and architectural vision
Portfolio level
Program Portfolio Management highest decision making responsibility;
Enterprise architect fosters adaptive design and engineering practices, and drives strategic architectural initiatives for a SAFe Portfolio
Epic owner responsible for coordinating portfolio epics through the Portfolio Kanban system
Backup: Definition of artifacts, events and roles of SAFe
Event
Team level
Iteration
Iteration Planning
all team members determine how much of the team backlog they can commit to delivering during an upcoming iteration
Iteration execution
Team demo team reviews the increment that results from the iteration
Iteration retrospective team member discuss their practices and identify ways to improve
Program level
Innovation and planning iteration
estimating buffer for meeting PI objectives, as well as providing dedicated time for innovation, continuing education, and PI planning and Inspect and Adapt (I&A) events
System Demo
demonstration of the subject system being built by the ART; test and evaluate the full system that the Agile Release Train is working on and to get feedback from the primary stakeholders
Inspect and adapt
held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated
Program Increment Planning
a routine, face-to-face event with a standardized agenda that includes presentation of business context and Vision, followed by team planning breakouts wherein the teams create the plans for the upcoming Program Increment
Value stream level
Solution demo
results of development efforts from the Solution Train are made visible to customers and other stakeholders
Pre- and post- PI Planning
for multiple ART; supports and coordinates the ARTs involved in the value stream; build a plan for the next PI
contains user and enabler stories that originate from the program backlog, as well as stories that arise locally from the team’s specific context
Program level & Value Stream level
Program Backlog and Value stream backlog
prioritized list of Features that have been analyzed and are intended to address user needs and deliver business benefits for a single Agile Release Train
Portfolio level Portfolio backlog
highest-level backlog in SAFe; provides a holding mechanism for the upcoming Business and Enabler Epics intended to create a comprehensive portfolio solution set
Architectural runway
consists of the existing code, components and technical infrastructure necessary to support implementation of prioritized, near-term features, without excessive redesign and delay
Solution Context
identifies critical aspects of the operational environment of a solution; essential understanding of requirements
Solution intent
critical knowledge; basic understanding of the current and evolving requirements
Backup: further related work
Turetken (2016): Development of a maturity model
lack of a well-structured gradual approach for establishing SAFe
before and during SAFe adoption, organizations can benefit from a uniform
model for assessing the current progress and create a roadmap for the
initiative
To address this need, a maturity model that provides guidance for software
development organizations in defining a roadmap for adopting SAFe is