Agile Principle # 12 defines that at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. From Scrum to Kanban and other agile frameworks, this is accomplished through retrospectives and continuos improvement processes. The key to being a successful agile practitioner is to identify areas of improvement and then experiment ways of improving it. But it doesn't stop there; positive improvements ultimately become success stories for other teams and motivates them to experiment with newer ideas which eventually leads to innovation. A negative outcome isn't bad either since it adds to the experience of situations where ideas may not apply. Thus the key to this process lies in being a child, an explorer, and inculcate an experimentation mindset. The SLICE framework addresses this in the following way:

  • S hare: Share an area of improvement
  • L earn: Explore the area for ways of improvement
  • I mplement: Search & apply the learning to identify the success factors
  • C ollateral: Publish blogs, white papers, presentations, etc. as observations of the implementation
  • E xpansion: Grow, Seed, and Split in order to explore new venues for success

In this workshop, I create an environment that inculcates an experimentation mindset and utilize the SLICE framework to drive the exploration.

 
8 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Discussing the benefits of being an innocent kid
  • Discussing the frameworks used by kids for experimentation
  • Introducing the SLICE experimentation framework
  • Exercise for participants to inculcate the experimentation mindset
  • Benefits to agility and current running experiments
  • Q&A

Learning Outcome

  • Inculcate a mindset of continuos improvement
  • Embrace failure as a route towards success
  • A framework for structured experimentation
  • Curious mindset that makes innovation a habit

Target Audience

Curious intrapreneurs motivated by continuous improvement.

schedule Submitted 7 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Balaji Ganesh N
    By Balaji Ganesh N  ~  7 months ago
    reply Reply

    Hi Vishal,

    Your proposal sounds interesting. But the slide deck does not give enough details on the outcome you are trying to achieve.

    The audience would be more connected if you can share some examples of where the SLICE framework and how it helped inculcate the experimentation mindset.

    Also, can you please elaborate on the exercises / activities that you are planning to conduct and how will these be structured within the 45 minutes talk.

    Balaji

    • Vishal Prasad
      By Vishal Prasad  ~  7 months ago
      reply Reply

      Hi Balaji,

      Thank you for your comment. I usually keep my slides less verbose so they just provide a direction to what I'm speaking instead of taking the complete attention of the audience.

      SLICE is a framework that I've been working with since the 3 years now. It's basically a structured approach for experimenting with process and product improvements.

      The essence of this session is to inculcate a mindset of experimentation among teams within organizations. Unfortunately what I realized a few years back is that most of the people are more attracted towards structured approach instead of disruptive innovation, even if it relates to experimentation or R&D.

      Here I address the four quadrants of human behavior that form the basis of experimentation: Curiosity, Exploration, Learnability, and Questioning. The reason I begin with the notion of being a kid at heart is because each human by nature possess these behaviors but lose is somewhere along the way as we grow up. These inherent behaviors make humans different from other species and have been the primary reason for innovation.

      The second part of the presentation talks about the SLICE framework and how it's similar to any science experiment that students conduct in schools. Once an improvement area has been identified through any method of retrospection (S in SLICE), the framework provides an approach to identify and execute the actions followed by a cascading effect that formulate the good practices of an organization. This makes it possible to continuously improve an organization's processes & products by fostering creativity & innovation. A major focus is also to understand that the framework embraces the concept of failure by focusing on learnability, thus incorporating the aspect of safety ... one of the principles of Modern Agile.

      During this session, I conduct an activity of 15 minutes with the audience by executing the SLICE framework to improve one of the most frequent processes preached by many agile frameworks (usually the daily stand-up but can be other, I let the audience decide) and sharing the outcome with everyone. This is followed by 3 success & failure stories that I've encountered with SLICE, including the active Meetup groups that are spin-offs of the framework.

      That pretty much provide a gist of my transcript: 5 mins of build-up. 10 mins of SLICE theory, 3 iterations of activities (5 mins each iteration), 10 mins of success & failure stories, 5 mins of Q&A.

      Also, I would like to convey that although this session is about teaching SLICE framework, it's more about making the audience think about the importance of experimentation in small chunks in-order to improve continuously. After all, this mindset is what brings in the creativity and innovation, probably the reason why one would adopt agility in the first place. Hope this provides the information you were looking for.

      Regards,

      Vishal

      P.S.: I'll be presenting this topic at the DiscussAgile Day Conference in Pune on 27th Nov and I'll try and get the video uploaded here.

  • Mahesh Raja
    By Mahesh Raja  ~  7 months ago
    reply Reply

    This sounds really interesting. Taking me back to my childhood to learn how can I get better as an Adult sounds interesting. :)


  • Liked Nilesh Kulkarni
    keyboard_arrow_down

    Why one size doesnt fit all? - Selecting scaling framework.

    Nilesh Kulkarni
    Nilesh Kulkarni
    Senior manager PMO
    Allscripts
    schedule 7 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Why one size doesnt fit all?  - Selecting scaling framework.

    This session will focus on what are the aspects organizations should consider when they want to scale agile implementation in organization.  There are several frameworks out there like SAFe, LeSS, Spotify, and so on. what is it that organization is trying to achieve and how a systematic approach of scaled agile implementation can help the organization.

    Attendees will be able to understand what aspects should be considered before organization decides to scale agile.  How to scale agile and when to do it largely depends on what organization is trying to achieve. Each organization is operating it in different way so there is no defined formula or framework that will work for all. But guidelines from this session will help the members to identify their needs and then take further action.  These guidelines can help the organization to successfully scale agile irrespective of which framework is selected.

  • Vishal Prasad
    Vishal Prasad
    Project Manager
    Springer Nature
    schedule 7 months ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Technical debt is a very common phenomenon; in fact it occurs with virtually every line of code whether you want it or not. Although unoptimized coding due to the rush presented by management pressure may be one of the major reasons for technical debt, it occurs in various flavors based on the nature of execution. Sometimes, even the best written code may run into debt by introducing a minimalistic change in the business definitions, e.g.: a variable name that makes no sense anymore.

    This debt cause and effect is exponentiated when scaled teams come into play. In many cases these teams are distributed and an optimized code for one team may become a debt for another. These debt dependencies between teams is what creates the "Valley of Debt". Unfortunately these cannot be avoided but good engineering practices coupled with lean principles may keep them confined for long enough in order to push the validity of software applications.

    Sooner or later, the cost of change will outweigh the benefit of an application and turn it into legacy; the challenge is to keep it as far as possible by slowing down the fall into the valley of debt. In this (non-PPT) interactive workshop, we will witness first hand how debts are introduced and how these can be confined by utilizing good engineering practices coupled with lean principles.

  • Liked AnkitTandon
    keyboard_arrow_down

    DIY Scaling Agile Framework

    AnkitTandon
    AnkitTandon
    Scrum Master
    Citibank
    schedule 7 months ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Is the scaling framework your organization is on helping you to be Agile or pretend to be Agile? How about drafting one that stays true to Agile principles and helps with what your organization needs most while scaling

    While there are a many frameworks available to scale Agile it is important to see if these prescriptions address the real problems that an organization have while scaling up.  Does one size fits all? Is it worth adopting a framework and then retrofitting your organization into it or it makes more sense to understand the dynamics of your organization, the existing challenges and business objectives and carve out a scaling approach, keeping Agile principles intact, that suits the organizations needs best.

    This interactive workshop is about discovering the best approach to create your own scaling framework, one that is custom made to respond to your organization’s needs. 

  • Liked Vijay Wade
    keyboard_arrow_down

    Sick and Tired? You don’t need a Physician: Try Personal Kanban

    90 mins
    Workshop
    Intermediate

    All of us are simply getting stressed because of multiple events happening in our life and hence we are not able to achieve the greatest goal of our life in time and sometimes never.

    This session I shall talk about why this is happening to you and what is the solution.

    Idea of this session is to shed some light on power of Personal Kanban and real life examples to save from being Sick and Tired 
    Kanban can be implemented in most walks of life. Knowingly or unknowingly few of us use it in few aspects of daily routine.

    It would be focused on ways to improve productivity in your life and achieving your goals and biological and psychological aspect of it....

    It would be a workshop mode session where in we would understand whats happening to us in our life and activities that lead us in this situation and will figure out how to get out of this and lead to successful life (Personal and Professional).

  • Liked Kamlesh Ravlani
    keyboard_arrow_down

    Agile at Scale For Innovation and Growth

    90 mins
    Workshop
    Intermediate
    Bringing innovative and breakthrough ideas to market doesn't have to slow down due to multiple geographies and scale of product development. In fact that's an added reason to be agile, test the product-market-fit early and reduce risk. 
     
    How can organizations benefit from being Agile at Scale For Innovation and Growth? 
     
    What are the wastes in the traditional organizational structure at scale? and What does it take to build customer value delivering feature teams?
     
    We'll dissect a case-study, Kamlesh Ravlani - the presenter, was involved with and learn how Google brought one of their innovative idea rapidly to market that involved multiple partners and teams in multiple geographies.
  • Liked Manjunatha M S Rao
    keyboard_arrow_down

    Agile Clinic – Strengthen Your Organization Agility

    45 mins
    Experience Report
    Intermediate

    When a company thinks about transformation or a change from legacy traditional software development models to Agile, they first think of bringing in External coaches or Scrum experts. In another situation when the companies want to increase their maturity in agile, they still will want to hire people from outside who are experts in this arena. This discussion is all about how we could groom people internally to sustain and increase the credentials within the organization rather than relying always on external coaches.

  • Liked Vijay Wade
    keyboard_arrow_down

    Study of Agile Practices Implementation in Distributed Software Development

    45 mins
    Original Research
    Beginner

    This session is intended to provide an overview of status of agile implementation practices.  The findings are based on survey data collated from selected agile practitioners from 14 different software organizations spread across the globe. The survey was designed based on agile manifesto and Twelve Principles of Agile Software Development and most commonly used Agile Scrum and XP practices. The survey includes 54% of response from new product development, 32% from enhancement projects and remaining 14% from maintenance and support projects. Results are summarized as most effectively implemented practices, most widely recommended practices, least implemented practices and practices which always need modifications / tailoring based on any given project or organization environment.  

    The objective of this study is following

    • To do an in-depth analyze of implementation of established agile practices from practitioners point of view based on data collected from the survey.
    • Understand any correlation the survey results are having with the already conducted surveys and published literature on Agile practices
    • Provide food for thoughts to practitioners community to fine tune or elaborate agile practices which may lead to update of standard reference materials

     

     

     

     

  • Liked AnkitTandon
    keyboard_arrow_down

    Agile contracting- Starting with the right mindset

    AnkitTandon
    AnkitTandon
    Scrum Master
    Citibank
    schedule 7 months ago
    Sold Out!
    45 mins
    Workshop
    Executive

    One of the biggest challenges in achieving agility is the way contracts are written. More often than not, these contracts prove to be a deterrent to realize the ultimate benefits of Agile. The way contracts have done traditionally usually go well with the traditional way of building software where scope / time / cost are fixed. However when the focus is on delivering business value early to the customer for his competitive advantage, to reduce risk, cost by not building what is not needed, gain and retain users, traditional contracting does not help the cause. Agile is something that the entire organization has to embrace. It has to start with the sales team. It has to reflect in the contract. It has to start with the right mindset. It has to start with an Agile contract.

    Third value of Agile manifesto is Customer collaboration over contract negotiation. Not only should this collaboration be expressed during project development, it should be expressed in the contract language as well.

    In this talk + workshop session, I will be sharing various types of contracts that can be leveraged / customized for an Agile project, some good practices surrounding them and will be involving the participants into a small workshop of writing Statement Of Work (SOW) for Agile contracts related to a few real world scenarios.

  • Liked AnkitTandon
    keyboard_arrow_down

    Performance management in Agile: Time to plug the hole

    AnkitTandon
    AnkitTandon
    Scrum Master
    Citibank
    schedule 7 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Principles behind traditional performance management system are utterly opposite to that of Agile. While traditional one focuses on Individual ratings, surprises, one sided evaluation, Agile is built on the foundation of trust, transparency, respect and courage. Whole is greater than sum of its parts and individual ratings and outdated performance management processes may prove to defeat the bigger purpose. While aspiring for Agility both at team and organization level, it is important to ensure all the wheels are moving in tandem in the same direction. Technology has changed the way our people engage, work and communicate and the need for frequent and less formal points of progress reviews is in demand.

    Agile performance management is an attempt to plug the hole by providing an approach that compliments Agile values and proves to be a catalyst than detractor for a high performing team and organization.