The secret sauce of Self-Organization

In this session, we discuss about the few facilitation techniques that a servant leader need to have to promote self-organization.

We also focus on Evolution of an Agile team, the traits of an agile leader and various of pit falls that do not lead to self organization.

How do you really make a team being controlled by a manager to become self- coordinating team?

We also look at key behaviours that helps changes stick.

 

 
4 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Presentation

Video

Hands on exercise

Closing

Learning Outcome

Fostering Self-organization organization

Target Audience

Scrum masters, managers, Senior Roles

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Anand Bagmar
    keyboard_arrow_down

    Enabling Continuous Delivery (CD) in Enterprises with Testing

    Anand Bagmar
    Anand Bagmar
    schedule 2 years ago
    Sold Out!
    60 mins
    Case Study
    Intermediate

    The key objectives of any organization is to provide / derive value from the products / services they offer. To achieve this, they need to be able to deliver their offerings in the quickest time possible, and of good quality!

    In such a fast moving environment, CI (Continuous Integration) and CD (Continuous Delivery) are now a necessity and not a luxury!

    There are various practices that organizations need to implement to enable CD. Changes in requirements (a reality in all projects) needs to be managed better. Along with this, processes and practices need to be tuned based on the team capability, skills and distribution.

    Testing (automation) is one of the important practices that needs to be setup correctly for CD to be successful. But, this is tricky and requires a lot of discipline, rigor and hard work by all the team members involved the product delivery.

    All the challenges faced in smaller organizations get amplified when it comes to Enterprises. There are various reasons to this - but most common reasons are - scale, complexity of the domain, complexity of the integrations (to internal / external system), involvement of various partners / vendors, long product life-cycles, etc.

    In such situations, the Testing complexity and challenges also increase exponentially!

    Learn, via a case study of an Enterprise, a large Bank, the Testing approach required to take them on the journey to achieving CD.

  • Liked Rishi Srivastav
    keyboard_arrow_down

    Becoming Agile : Get back to first principles first

    Rishi Srivastav
    Rishi Srivastav
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Talks about partial successes with Agile implementations. We have become iterative for sure and there is a definite sense of cadence. But concept to cash lead times are still quite high. A sense of dogma has crept in the rituals, they happen, but there is little soul.Team members are still quite stressed out; We have avoided the famous waterfall death march for sure but it is still a very tiring and painful long march.  Organisations doesn't feel that they have reaped all the benefits which were promised. There is just a handful of companies who seem to be living the values and are  really nimble in the market place. What went wrong?

    Our focus on people, value, flow and quality instead of process,tools, cost, schedule and scope, got the attention but did not get internalised by all. So while we are adopting “Agile” methods we have not become “agile” yet.

    There is a need to get back to first principles. There is a need to explain knowledge workers on the ground “Why” the principles work. Leaders need to do more than just support the change, they need to know, behave and do the right things. Lastly people do need to learn and love their craft. Yes, it is about money but is it also about autonomy, mastery and purpose.

    The session takes through key concepts around people, business value, product development flow and quality via fast feedback, and invokes people to understand and let their team understand the basic principles  first to lay a strong foundation, before building an Agile enterprise on top of it. It is only then the “real transformation” happens and the products get in front of the end users faster.

  • Liked Prasad
    keyboard_arrow_down

    Movers n shakers of Enterprise Agility

    Prasad
    Prasad
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    With business agility the new watchword in senior management circles, more and more enterprises are looking for ways to adopt ‘agile’ into their technology practices. However, such an initiative needs to go beyond the mere adoption of agile in a few projects. To successfully implement enterprise IT agility, organizations need to understand the impact of agile across functions and groups, develop frameworks to sustain agile, empower teams across the board to work in an agile fashion, and invest in the right infrastructure. A strategic roadmap based on these considerations can help organizations infuse agile into their practices, processes and systems, thereby achieving true benefits of agile – faster returns, better quality and quicker time-to-market.

    This session  discusses the critical factors for an effective roadmap to implementing enterprise IT agility. It also outlines how these factors contribute to a successful enterprise IT agility strategy.

  • Ebin John Poovathany
    Ebin John Poovathany
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    This is a workshop to introduce the concept of Value and cost based prioritization. The speaker will facilitate a short game for participants to learn how to prioritize the backlong using value and cost. 

  • Liked Om Prakash Bang
    keyboard_arrow_down

    Agile Business Analyst and Product Backlog Management

    Om Prakash Bang
    Om Prakash Bang
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Agile Product development with Scrum is based on completing a set of User Stories within a time-box called a sprint. Stories describing user functionality. Conversatin with customer is the means of elaborating requirement. looks simple, right?

    Only User Stories are enough for product development? If not, what all other documents are necessary and how these are progressively elaborated? 

    What's required before agile team start sprinting? What are the challenges while transitioning from waterfall to agile related to product requirement?

    What's the role of Business Analyst in agile? BA moving into an agile team, moving to Product Owner? Can Business Analyst and Product Owner co-exist?

     

  • AnkitTandon
    AnkitTandon
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    -The Sprint Planning meeting is just too long and never finishes on time.

    -I finished my tasks on time, the story couldn’t be completed as there was a dependency on him. I just didn’t have time to follow it up. Not my fault.

    -Yet again, there are left over items in the sprint. We couldn’t finish all the committed stories as some of them were too complex for their correct effort complexity estimation.

    -Ohh Gosh, once again the priority of the tasks have changed in the middle of the sprint, there are new urgent items that have to be done. My sprint commitments have gone for a toss.

    -We moved to Agile from waterfall and it has been few sprints into it, though even here vision is unclear, requirements are evolving and our sprint commitments are failing. Velocity is just been a number, Burn down graphs conclude nothing concrete and useful.

    -How do we cater support/maintenance work with Scrum?

    Does any of the above statement sound familiar to you, if yes probably it is the time to evolve and adopt KanScrumBan wrapped around XP practices.

    KanScrumBan is the combination of Kanban and Scrum and uses the best features of both. While Scrum framework helps the software development teams to self-organize, collaborate, improve efficiency constantly, work in small iterations, and avoid management overhead, applying lean methods like Kanban , flavored with XP practices can extend these benefits.

  • Liked Vineet Patni
    keyboard_arrow_down

    Lean - Agile: The Eternal Siblings

    Vineet Patni
    Vineet Patni
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Intermediate

    What came first - Lean or Agile? It's a chicken-and-egg question for many. And then, there are beliefs that these two are separated twins.

    If you think that Lean software development and Agile are the same, think again!

    There are both difference and similarities in the Lean and Agile principles and practices.

    During this talk, we will discuss on how Agile and Lean are related or different. Or are they two different names of the same thing? how the principles of Lean and Agile can be leveraged in order to create complex software solutions at enterprise level.

  • Liked Amogh
    keyboard_arrow_down

    Team Agreements - A way to make self organized team

    Amogh
    Amogh
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Intermediate

    Why do we need team agreements?

    Scrum teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. To become self-organized, a team has to go through various stages of team development.

    Tuckman's stages of team development The "forming, storming, norming, performing" model of team development was first proposed by Bruce Tuckman in 1965. He maintained that these phases are all necessary and inevitable in order for a team to grow, to face up to challenges, to tackle problems, to find solutions, to plan work, and to deliver results.

    A Scrum team does not have the luxury to be in each of these stages for much time, as it is expected to deliver right from the first sprint. Thus the need for formulating team agreements arises at an early stage. Sprint Zero is the ideal time for a Scrum team to go through all of these stages within a very short period. As Scrum is iterative and incremental, a Scrum team goes through Tuckman's stages in each sprint and improves its performance in every new sprint.

    Knowing what kind team agreement a Scrum team might need is useful for the team members. It helps avoid conflicts. This knowledge can help them set the team agreements in advance during Sprint Zero rather than deciding what should be done at the last moment, in the middle of working sprints. Team agreements can be defined and agreed upon in a meeting facilitated by the ScrumMaster. Various steps that can performed in this meeting are: prepare, brainstorm, sort, categorize, agree, and refine

  • Liked Sekhar Burra
    keyboard_arrow_down

    Maturing the Agile way-The Road map for Continuous improvement

    Sekhar Burra
    Sekhar Burra
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Maturing the Agile Way contains 2 Agile maturity models, Qualitative and Quantitative model, deals with the concept of Organizational comparative Agile maturity index, which quickly and reliably determine how agile an organization is compared to other organizations. This company Which had been adopting Agile over several months, wanted to understand realized business benefits in terms of more reliable, shorter, milestone releases and improved quality (as measured by defect introduction rate). However, most often those with visibility across the full adoption effort many times noted that the adoption of Agile had been "uneven," and wanted to take the adoption effort "to the next level." This in turn may give room for improved agility with many more areas in which additional business value could be added.

    The goal of taking the agile maturity assessment was to better understand the areas on which the company should focus next. Based on the results of their assessment, the company may decide the need to emphasize improvements on few focus areas during particular time period.

    This presentation also contains Scrum Master Maturity index, to create a learning plan for Scrum Master towards continuous improvement.