The different engagement models, processes, challenges and solutions for a distributed Scrum Team in an outsourced product development (OPD)
A distributed Scrum team is a necessity than a choice in many cases. Often customers and their suppliers struggle to put up a team model that will work effectively and provide maximum value. The customer wants to be absolutely sure how the entire engagement will be executed so that there are no surprises later.
So, what are the different ways of forming teams in a distributed environment, what is the impact on the execution, how do you execute different engagement models, what challenges do you see and so on? These are the questions the customers are interested in.
This talk will focus on answering the above questions. We have defined 3 types of distributed team models and implemented in few of the projects in an onshore-offshore scenario. We have also tailored scrum meetings like planning, DSM, etc. so that these meetings are more effective in distributed model. While some of the changes have worked, some still needs to be enhanced further.
Outline/structure of the Session
- Scrum models for OPD
- Explain the 3 types of team structure models that can be implemented in an OPD
- How do you decide which model to choose
- Scrum Process tailoring
- Explain scrum ceremonies that needs to be tailored for each of the models
- Elaborate more on one of the models
- Benefits and challenges
- Explain what has worked and not worked
- Explain the challenges, solutions and benefits achieved
You will learn
- The 3 types of distributed team models for Scrum teams
- Know how to go about the different scrum ceremonies for each of the model
- The documentation and communication modes
- The challanges and solutions of each model
Management, Project Managers, Scrum Masters, Scrum teams
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Meeting the challenges of agile principles: An offshore Scrum Master perspectivePooja Wandile
schedule 3 years agoSold Out!
The 12 agile principles lay the foundation for a successful agile team and deliver a product that meets customer satisfaction. Every principle is an absolute necessity to build great software and great teams. While these principles have stood the testimony of time over a decade now, much has changed the way we build and deliver software, especially from an offshore perspective. Adoption of agile methods does not simply imply a framework or a process implementation, but it goes beyond that.
In this talk, I share the experience of a Scrum Master, who in hindsight, look at the challenges such as lack of trust, micro management, lack of technical excellence, managing stakeholder’s expectations etc. and the impact on team’s performance. This is the result of ignoring agile values and principles which could have been avoided. Lastly, we look at the actions taken by the team and Scrum Master to turn on the challenges into a win-win situation for both onshore and offshore teams and become one of the successful agile teams.
How do I know if Agile is working for me or not? – An Executive’s Dilemma
As Agile coaches, several times when we talk to the Sr. Management in a company to taking agile to a bigger level and adopt it across their business units a common response we get is "I have seen agile working for our project teams. I am also in midst of an agile transformation where we are applying it in large programs. But how do I know the transformation is helping me achieve my goals at an organizational level. Our organization typically tracks executives on finance, people & delivery parameters. In an agile context, how do I ensure that I am on track with the executive-level dashboard (finance, people and delivery)?" As part of this session, we plan to share our experience of how "Balance Score Card" technique was implemented at one of the financial services company following agile. By using concept of balance score card we were able to map the agile goals with the IT organization goals and ensure that the agile methods were giving the desired results.
Fixed FAIL Projects - Failure guaranteed!Prashant Sagar
schedule 3 years agoSold Out!
After having seen multiple projects fail, I was intrigued to research on if there are any patterns to avoid.
Customers dint clearly define what they value most and Vendors dint ask.
Who do you blame?
Customers find it easy to blame Vendors while Vendors fall back on the signed documents and dont shy away either from the blame game.
When both Customers and Vendors are losing, why are we not changing our game?
Learn from one person's experience to avoid burning hands, missing projectd deadlines, missing requirements and to avoid going through exhaustive mud slinging litigations.