Building a self-organizing and sustainable Communities of Practice by WorkingOutLoud!
In any large scale Agile transformation journey, it is very important to build and sustain continuous improvement culture. What choices are available beyond regular retrospectives and Inspect & Adapt workshops to identify and address improvement opportunities in a systematic approach?
Communities of Practice help create a forum for interested individuals to learn from each other and external resources like eminent speakers, video recordings, books, etc. However, many learnings through these Communities of Practice activities very often doesn't always get converted into practical immediate to short term application. Therefore, the participating individuals gradually loose their interest in such COPs and within in a short time span, such COP initiative meets with its natural end. This leads the COP champions (or promoters, which typically would be Agile Coaches in cases of Agile Transformations) to wonder: what could be done to create an self-organizing environment for continuous improvement that yields tangible results to individuals and their teams/organization?
Above questions were encountered by us in our current Agile transformation engagement and in response, we discovered the WorkingOutLoud concept from John Stepper. This model sounded like a perfect opportunity to experiment with our attempt to build a self-organizing and sustainable Community of Practice to promote continuous improvement culture at the overall organization level. In this talk, we shall share our approach and learnings from this experiment.
Outline/structure of the Session
- What is a Community of Practice (COP)?
- Why Communities of Practice initiatives generally fail to sustain beyond initial few months?
- What is WorkingOutLoud (WOL)?
- COPs & WOL - our approach of applying 12 weeks of WOL to COPs
- Learnings from our experiments
Participants will understand how to use structured and innovative learning approach to build Communities of Practice in a more sustainable way which provides better momentum for organization level Agile transformations.
Agile coaches, senior leaders in the organization, managers, scrum masters, developers, testers etc.
Participants should have some knowledge of agile ways of working. However, the core learnings can be easily applied to non-agile teams and organizations too.
schedule Submitted 1 week ago
People who liked this proposal, also liked:
Puneet Khanduri - Democratizing Machine Learning at TwitterPuneet KhanduriML & AI Services Lead - Cortex
schedule 1 month agoSold Out!
Twitter has rapidly evolved in how we do Machine Learning over the last few years. We rapidly evolved from making incremental improvements to our existing Logistic Regression models to a wave of new Deep Learning architectures. At the same time, we were faced with the challenge of uneven distribution of ML expertise across the company. This is the story of the Cortex team that enabled this machine learning transformation across the entire company by making a set of careful strategic investments.
Vishweshwar Hegde - Mindfulness@Work: B-D Framework – Accelerating Enterprise Agility CultureVishweshwar HegdePartner, PM Power ConsultingPM Power Consulting
schedule 4 weeks agoSold Out!
Business Agility is achieved through proactive & quick sensing of Customer/Market needs and fulfilling those needs through end to end collaboration of Customers, Business Functions and Solution Delivery Functions in a seamless flow. Apart from technology and process elements, the critical success factor for such functioning is the mindset and culture aspects of people and organization units across the value chain. Mindfulness is a great tool to develop Emotional Intelligence which is the bedrock of leadership tenets for Agility Culture like proactiveness & self-organizing, cross-functional collaboration and facilitative leadership styles.
This session covers a case study of Enterprise wide Mindfulness transformation in a 2000+ strong global Technology company. The session covers aspects of:
- Creation of a Mindfulness@Work framework called B-D Framework – Being Mindful and Doing Mindfully. Being Mindful by Being Aware, Alive and Calm; Doing Mindfully by Perceiving Immersivity, Processing non-judgmentally and Performing Empathetically.
- Mindfulness techniques and practices at individual level like BreathWatch, BodyScan, Balanced Breathing, Journaling.
- Organizational and Team ceremonies to inculcate Mindfulness as part of work practices like Mindful Meeting, Sense Walk.
- Results captured after 6 weeks of practice of Mindfulness practices by the participants on Personal Wellbeing, Personal Effectiveness and Professional Performance.
- Organizational Change Management including unique role called Happiness Evangelist.
The session will be a joint presentation by the Happiness Evangelist and the Mindfulness Coach.
Fennande van der Meulen / Maartje Wolff - How to build good habits in an Agile TeamFennande van der Meulenco founderHappy OfficeMaartje WolffCo FounderHappy Office
schedule 1 month agoSold Out!
Culture eats strategy for breakfast, said Peter Drucker. We all agree to that. If our organisational culture is not building up to our goals, we will never reach them. The main question is, how can you create an organisational and team culture that contributes to your goals, to productivity and success? The key for change is to form the right habits, within our agile teams. Like exercising regularly and losing weight you can develop habits for being healthy, happy, more productive and successful at work. Therefore it is important to understand the human nature and its potential for transformation. In this workshop participants get all the insights and best practices to develop habits for an happy and fulfilling (work)life and organisational culture.
Mangalam Nandakumar - Why story points make no sense for a product companyMangalam NandakumarDigital SpecialistMcKinsey & Company
schedule 1 month agoSold Out!
T-shirt sizing. Fruit Sizing. Planning pokers. You might be familiar with any or all of these estimation (relative sizing) techniques. Story points based estimations (along with velocity mapping) is touted as a predictable method to plan for software delivery. Teams are expected to get a good sense of the effort needed to deliver a piece of work by comparing estimates with references of similarly complex work they have delivered in the past.
The accuracy of point based estimates fares more or less in the same range as sheer gut feel. So, the natural inclination for software teams is to try and make it more accurate than gut feel. Thereby, we obsess with breaking functionality into smaller byte sized stories. We freak out when there is "scope creep". We debate endlessly about ideal days vs. person days. We fuss over the specific visual representation for the burn-up or burn-down.
Does it matter anymore how many days the team spent chipping hard at a feature that added no value to the business? Have we made agile teams into mini waterfall teams by focussing on the wrong metrics? Can product companies afford this?
Process heaviness in product companies can cost a lot. We need to find better ways to invest in success metrics. We need to change the conversation from productivity to value add.
My talk intends to challenge prevalent estimation practices and contest their validity in product companies. I will also introduce ideas around capturing relevant business metrics and sizing stories using business value.
Manjunatha M S Rao / ashish kumar / Shijo Paul - Product Quality Improvement Via Defnition of Done (DoD) and Tech Debt reductionManjunatha M S RaoAgile ExpertCisco Systemsashish kumarSenior Engineer/Scrum MasterSunGard Global SolutionsShijo Paul-Cisco Systems
schedule 1 week agoSold Out!
Product quality plays a key strategic role in any organization success. Organizations have tried and tested many tools, techniques, methodologies or mechanisms to achieve best possible quality while trying to meet time to market demands. Agile methods have gained prominent attention of CXO as a strategic piece for IT and Business alignment. Many organizations have embraced agile journey in recent years and have reported noticeable improvement in product quality, customer satisfaction, early value delivery (Time to market) and increased people engagement at workplace.
One of the magical factor driving product quality improvement in Agile Scrum is Definition of Done( DoD). A well thought and implemented DoD keeping Tech Debt as a reference would result in significant improvement of Product Quality.
This paper provides summary of our experience of implementation of DoD, Tech Debt reduction strategy and magnificent results we observed in an enterprise level large complex legacy system.