Self Managing Game Storm - How to form self designing teams
For transformations to be successful, typical Component teams are giving way to self managing, cross functional teams, organized by customer value (Feature Teams)!
These Self-managing teams are the basis of Scrum, where the team has the authority to design, plan, and execute their task and to monitor and manage their work process and progress. The team rather than a (project) manager—has the responsibility of deciding how to work.
But Self-managing teams do not just happen by chance. Instead they need the right environment. The organization is responsible for supporting the team development by creating the conditions needed for the teams to succeed and the real empowerment starts when the teams are 'self designed' from the beginning - which means that team members choose their teams to work!
This workshop will showcase to the participants HOW they can form 'self designed' teams, and experience the joys of 'self organization'.
Outline/structure of the Session
* Background for Component Teams, Feature Teams - 5 mins
* Ideal Team Definition - 5 mins
* Market your Skills - 15 mins
* Cycle 1: Form Teams and Retrospect - 15 mins
* Cycle 2: Form Teams and Retrospect - 15 mins
* Cycle 3: Form Teams and Retrospect - 15 mins
* Review Teams and Choose Scrum Masters - 15 mins
* Q&A - 5 mins
* What is self organization and empowerment
* How to understand the team members strengths and weakness
* How you can help your teams to self-design and self organize
* How to build teams which deliver end to end customer-centric features
* How to challenge your organization's culture and hack it
Anyone who wishes to experience Self organization, including Executives, Agile Coach's, Scrum Masters, and Practitioners
Knowledge of Scrum
Awareness of "Feature Teams" would be useful
schedule Submitted 1 week ago
People who liked this proposal, also liked:
Prasad - A startup facilitated digital transformation journey of Europe's largest Insurance retailerPrasadPrasadHolleyHolland
schedule 15 hours agoSold Out!
Large Insurance enterprises find difficult to renew and find new ways to transform their customer experience, improve operational process and find new business models. As an experiment they engaged an insure-tech startup to lead their digital transformation journey.. This case study is about a point of view, approaches, challenges and cultural surprises that we faced during this journey..
The more we share more we learn!!
Asheesh Mehdiratta - How do you rejuvenate your fading Communities of Practice?Asheesh MehdirattaTransformation LeaderShell
schedule 1 week agoSold Out!
As part of organizational digital transformation journeys, CIOs are moving from hierarchical models to 'self organizing' Feature teams, in order deliver efficient and effective IT, but still need to retain the deeper functional expertise. Hence the growing importance of building and sustaining "Communities of Practices" (CoPs), as the traditional functional silos are broken down, with the transformation themes.
But if you are a Change Agent responsible for the Transformation, you understand how challenging it is to nurture, and especially sustain these CoPs.
So join my session, as I will share how I have used the ADKAR change concepts to form my own RECIPE for building, nurturing and especially sustaining enterprise wide Communities of Practice (CoPs).
You will pick up this simple framework, along with instant techniques, tips that you can apply, and learn from my experiences in overcoming the challenges of scaling communities, and working with distributed communities.
You will be able to recognize the success and failure patterns, and in the end will walk away with practical advice on building "long lived" Communities.
Come join my session to change your WORLD!
Ashok kumar Pandey - Raising Digital Quotient of highly regulated financial institution with Monolithic to Microservices JourneyAshok kumar PandeyEnterprise Agile and DevOps coachInfosys LTD
schedule 1 week agoSold Out!
1) What was problem?
Longer release cycle time, ever increasing code base, tightly coupled
functionalities of application making difficult to implement change, complex
2) How we have approach towards problem: -
A) People transformation: - New organisational design where people are
responsible for making and running small set of Microservices. The services are
defined based on bounded context by levering Domain Driven Design.
B) Process transformation: -In order to identify the organisational process bottle
neck, End to end value stream mapping done and Improvements themes such as
change management, release management etc has been implemented.
C)Technological transformation: - New technologies, tools and practices adopted
that has helped in achieving engineering excellence by Automation,
Autonomation ,CICD, Infra as a code, cloud only infra , Microservices and API
led economy etc.
3) Our Approach towards Microservices :-
1. API led connectivity: - Composiblity of different system is the key for
Microservices experience and we can achieve the composiblity of
different system by leveraging API led connectivity approach. In this
approach, we will have system API, process API, and experience API.
System API takes cares of system of record underpinning the service,
process API takes care of business process underpinning the service and
Experience API is responsible for experience of consumer of services.
2. Elements of API design:- In our API design we have used domain
model , architectural standards , API catalogue ( experience , process ,
system) to identify development details, stub details , deployment
details, RAML specification ,data mapping ,back end system
specification and integration specification.
4) Client –Server Monolith application to Microservices application: -
1. Strangler pattern of Microservices: - In client –server monolith
application to Microservices application journey, we have used the
strangler pattern of Microservices. As we can see from architectural
diagram that we have put the dispatcher (API gateway, reverser proxy)
in front of monolith and directed our clients to it. The dispatcher also
acts as an API gateway and provides utility such as Authentication and
authorisation, logging and Auditing. The dispatcher is just a proxy to
endpoints exposed by monolith. We have refectored each domain into
Microservices and deployed them into Microservices platform.
2. Swagger: - We have used swagger to define, generate and Document
3. Caching as a service: - We have implemented cashing as service and we
have cached the static data of system API, experience API, and process
API. Cashing helps in improving the user experience.
4. Configuration of the API security context: - Our API Gateway exposes
API to consumers and protects services using the policy enforcement:
5. Engineering excellence in Microservices landscape - We have achieved
engineering excellence by practicing CICD, Infra as code, automation
etc in Microservices landscape.
6. Other API design consideration: - a) Asynchronous event based
communication using the network for loose coupling between services.
b) Circuit breakers for isolating the failure of services c) Consumer
driven contract as way of service consumption.
5) When not to go for Microservices.
Sunil Mundra - Be Alive, Be AgileSunil MundraPrincipal ConsultantThoughtWorks
schedule 3 weeks agoSold Out!
The Key challenge organisations are facing today is having to deal with the exponential rate of change which is happening in the external environment. The extent and pace of change is so disruptive that no organisation, regardless of age or size can take their competitive advantage or even their survival for granted.
The main reason why organisations are struggling to change is that they are modeled as mechanistic or close-ended systems. On the contrary, all natural socio-economic systems essentially which are living systems have dealt with change very effectively since eternity.
This talk is about infusing life into organisations. The speaker will highlight the key characteristics of living systems which enable them to deal with change effectively and also suggest actionable guidelines that will help leaders/influencers to bring their organisations to life. This approach will enable organisations to not only survive but thrive on change.
Bernie Maloney - Bootstrap your Business Model - Business Agility on the Back of a NapkinBernie MaloneyAgile CoachPersistent Systems
schedule 1 month agoSold Out!
With every product we ship, we learn what we wished we’d known: what customers *really* wanted. What if you could gain those insights before beginning development? What if you could “unit test” a product idea? Or at a bigger level, what if you could “system test” your business idea/plan?
Engineering teams are experiencing productivity gains of 30-300% when applying Agile and Lean practices and methods. These same Agile and Lean principles can be applied beyond engineering, to the business itself. Using a lightweight yet powerful tool, assumptions behind a business plan can be tested and iterated almost on-the-fly. With a hands-on exercise, attendees will learn how to build a map of any business ecosystem, and how to use it to check and iterate solution viability. Come experience the application of Agile to Business so you and your team can focus on your richest opportunities over chasing your competitor’s taillights.
Bernie Maloney - Wipeout! Make *New* MistakesBernie MaloneyAgile CoachPersistent Systems
schedule 1 month agoSold Out!
Ever feel like the market moves faster than your marketing team? Or, wonder how flexible your finance (& leadership!) teams would really be if self-direction glitched and blew $1M? Organizations introduce Agile believing it will lead in part to greater responsiveness and resiliency. Yet, why do so many fail to achieve those outcomes?
It isn’t just that they’re structured and operated by default along hierarchical lines rather than by design for iterative work. Achieving the full benefits of Agile comes from shifting the culture and mindset of a whole organization, sometimes as radically as encouraging it to “Make New Mistakes.” This very philosophy was a driver in the fastest division in HP’s history to reach $1B, a hardware division that was focused on manufacturing operations, with razor thin margins, and markets that changed 3x faster than the development lead time.
Through a series of short stories and exercises, attendees will explore 5 practices from that business which led to roaring success. We’ll probe their parallels in Lean / Agile practice. With each one, you’ll briefly self-inspect the state of your own organization, as well as create a backlog you can use to adapt in your “real world” beyond the conference.
Do you have, or want, a vision that takes you beyond high performing teams, to a high performing, resilient business? Come hear how you can help your organization shift from mechanics that “do” Agile, and walk away with a feel for what’s possible when not just development, but a whole organization surfs the flow of “being” Agile.