


Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Two case studies that illustrate the importance of breaking down organizational silos and implementing agile software development. The first case study, from birla institute of technology & science, pilani, discusses how t-mobile employed techniques like value stream mapping and feedback velocity to eliminate silos between project managers and developers. The second case study describes a software development project for an international football event in the united arab emirates, where the team used agile methodologies to prioritize features and plan sprints. Students can use this document as study notes, summaries, or cheat sheets to understand the concepts of organizational silos, agile methodologies, and software development.
Typology: Assignments
1 / 4
This page cannot be seen from the preview
Don't miss anything!



Case Study-1: Breaking Down Silos Between PM & Dev. by T-Mobile Marks=7% YouTube: https://www.youtube.com/watch?v=7SGHStr4tZQ
workspaces can contribute to the creation of organizational silos. Employees may connect with colleagues who work in the same vicinity as them, which may be the same people they encounter on a daily basis. They may share the same communal spaces, such as break rooms or conference rooms, which increases their opportunities to communicate. They may not interact as often with coworkers who work on the other side of the building, for example. d. Tolerance from management: Leaders who tolerate silos allow the culture of separate groups to exist. The relationship between managers can also influence the morale of lower-level employees. For instance, a business has two chief officers who manage their own departments, but they disagree on what leadership direction to take. The tension causes their staff members to create organizational silos within their respective departments. Tools and Techniques used:
11 [API] Ground list page show available when canceled - (with four slots)
12 [API] Send notification to team members/coaches on confirmation
13 [Mobile] Send notification to team members/coaches on confirmation
14 [API] Coach should be able to make requests for any changes in ground selection
15 [API] Coach should be able to make requests for any changes in Schedule changes
16 [API] Request from a coach should be sent to the Facility team
17 [API] Request from a coach should be sent to the executive
Total User Story Points 70 Story Point for 1 developer: 12 Sprint required = Total User story points/ story points completed by 1 developer = 70/ 12 = 1. Sprint required = 2 (round off) Sprint required = 4 weeks Sprint velocity = 70/2 = 35