Come! Take a plunge with us into the world of Self Organization!

In agile teams there is a belief that the teams self organize. But do we really understand what this really means? The scrum guide simply says three things autonomous, self transcendent, cross functional.

In this interative workshop we will experience what self organization is all about via a fun filled game. You will go back with key learnings through your own experience. 

This session will be a combination of audience participation in activities, discussions combined with presentations and loads of fun!

This interactive game session is for anyone who wants to learn more about  being self organized and what makes the self organized teams tick.

 
36 favorite thumb_down thumb_up 11 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. 10 minutes - opening and Introduction

  2. 5 minutes - Working agreement and purpose.

  3. 15 minutes - We will present some of the well understood and researched concepts of self organization. This would include videos of some teams that naturally self organize.

  4. 15 minutes - Form into teams and teams discuss in groups on what is meant by self organization in software context, each team to document their findings with their questions. ( they will have to self organize to do this well )

  5. 15 minutes - Self organization game 1 - In this game we will create situations which demand teams to self organize. We will need a open space area to play these games.

  6. 10 minute - Retrospective on the game

  7. 5 minute - Team to modify what they did in 4 above based on learnings of the game.

  8. 15 minute - Q&A 

Learning Outcome

1) A clear understanding of what self organization is not about.

2) An ability to apply the techniques back in the teams

3) Scrum and its correlation to Self organization

4) Techniques to teach the concept of self organization to the management and team member

5) An appreciation that self organization is not easy and needs maturity in the team to make it possible

Target Audience

Anybody and everybody is welcome!

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • AgileSattva Consulting LLP
    By AgileSattva Consulting LLP  ~  1 year ago
    reply Reply

    Coaching approach applied to facilitate the session is very interesting. Would like to know if you would introduce the definition of the "Self organized teams with respect to Software development" to the audience, or will it be summation of their findings they have in their sub groups? 

    One of the key learnings you have mentioned is the "ability to apply technique back in the teams". Is there a technique that would be introduced? cos this is very much mindset related concept, would like to know how you would introduce techniques? Or is it the exercises that they can take back and use it with the teams?

     

    • Vibhu Srinivasan
      By Vibhu Srinivasan  ~  4 years ago
      reply Reply

      Deepak This is VIbhu here. I would like to say that "Self Organization" is a well spoken topic But it is also one that is generally misunderstood. Some common questions that get asked are " In self organized teams do every one do everything".  The goal is to present a series of learnings through self discovery that people can take back to work. We are not looking at just one game. Also the number of people in audience dictate what we do.

    • Kanchan
      By Kanchan  ~  4 years ago
      reply Reply

      Thanks so much Deepak. It will be both the ways. Intially, we would introduce the definion by research done by experts in this domain the past and our experiences through this journey. With this context, we will introduce game excercise where sub groups will sum their findings and we together we will figure out what we take back to our daily work.

      You can very well take the excercise back with your learnigs and use it with your teams back home.

      Does this help answer your question?

      Kanchan :)

  • Sonik Chopra
    By Sonik Chopra  ~  4 years ago
    reply Reply

    Hi Kanchan

    Very interesting topic indeed. Can you please provide some details on the games you would like to include in this workshop? I am sure our audience will enjoy this a lot.

     

    Regards

    Sonik Chopra

    • Kanchan
      By Kanchan  ~  4 years ago
      reply Reply

      Hi Sonika, Thank you for your encouraging response. Vibhu and I've couple of nice ones and we need to nail down more on it. Let us get back to you with more spefic reply early next week.

      Have a nice weekend!

      Thank you!

      • Vibhu Srinivasan
        By Vibhu Srinivasan  ~  4 years ago
        reply Reply

        Sonica,

        As Kanchan said we are still deciding the appropriate activities. What we know at a overall goal is

         

        "As a participant I would like to clearly understand "Self organization" by doing some activities " so that I can Apply this with my won work. "

        We are not planning a big large game with only fun in mind. Each activity will be 10 - 12 minutes long with a group of people. In a few weeks we will have this all flushed out. We are running these activities at some sessions now to learn more about the impact I will surely list it out when we have finalized

  • Ram Srinivasan
    By Ram Srinivasan  ~  4 years ago
    reply Reply

    Hi Kanchan/Vibhu,

    Can you please let us know the structure, and the mechanics of the game(s) that you plan on facilitating?

    Thanks,
    Ram

    • Vibhu Srinivasan
      By Vibhu Srinivasan  ~  4 years ago
      reply Reply

      Ram

      The strcuture we are thinking is a few small experiements in/ with the audience.  Which particular series of experienments is to early to tell. As Kanchan had pointed out, we had done an experiment where two groups built a vehicle ( cart ). One group was split by titles as Project Manager, tester other by roles/skills, welder,electical mechanic etc  We recorded this session then compared the two groups.

      In a few weeks we can probably tell exactly what we will be doing

  • Joel Tosi
    By Joel Tosi  ~  4 years ago
    reply Reply

    Hi Kanchan,

       An interesting submission.  The questions I have for you - I can easily understand the success and applicability of running this inside an organization with a complete team together.  What is your experience running this at a conference with strangers and how transferrable is that knowledge back to their organization the following week?

    Thanks much,

    Joel

    • Kanchan
      By Kanchan  ~  4 years ago
      reply Reply

      Dear Joel, Thank you!  I understand where you are coming from. This is not a team building exercise. Our attempt is to define self organization and understand what challenges it throws to the individuals. All this done via a game. For example, in one such attempt, one group organized themselves by titles/roles viz-a-viz the other group organized by skills. With all this, we will discover how we can be better after experimenting and observing ourselves going through these challenges.

      Does it help? 

      Kanchan

      • Vibhu Srinivasan
        By Vibhu Srinivasan  ~  4 years ago
        reply Reply

        Hi Joel

        Thanks for your feedback. To add to Kanchans point,  A few simulations will be based on some questions . We are hoping that people get enough clarity on this commonly misunderstood topic so that that they can go and apply ar correct themselves. It would be awesome if they can do this the next day


  • Liked Elinor Slomba
    keyboard_arrow_down

    Elinor Slomba - Scrum of One

    45 mins
    Demonstration
    Intermediate

    Artists tend to function in ways that are intuitively Agile.  Working closely alongside arts leaders for nearly twenty years before becoming a Scrum Master, I have devised a set of practices that solopreneurs, freelancers or anyone working without Agile support in a larger company can practice to become more productive and contribute positively to organizational culture.  I have been putting this into practice for managing deliverables with my own clients as a consultant.  Each practice has two parts.  For example, Scrum of One Timeboxing includes Step One: Give Yourself a Deadline.  Step Two: Blackmail Yourself by Putting it in Print.  Another is Scrum of One Product Ownership Step One: Figure out who your patron is. Step Two: Show them your works-in-progress and ask for feedback.  A particularly powerful practice is Scrum of One Standups Step One: set up regular times to meet on a given project.  Step Two: keep to the schedule, and if you're the only one who shows up, document and report on the hurdles you're facing.  Scrum of One can help many more people adopt the Agile mindset that is a precursor to smooth collaboration on teams.  

  • Liked Bernd Schiffer
    keyboard_arrow_down

    Bernd Schiffer - Net Promoter System for Agile Companies

    45 mins
    Talk
    Intermediate

    Customer collaboration is essential to every Agile business. To create and collaborate to keep a customer is the purpose of an organisation. But still lots of companies try to make bad profits, i.e. profits earned at the expense of customer relationships. The Net Promoter System (NPS) is a renowned open-source system which addresses and measures customer collaboration. And did you know that you not only can use it to get feedback on your products and services, but also on your employees and your personal performance?

    NPS is a perfect fit for Agile companies - and those who want to be. Most of the companies I worked with (Agile coaching, training, consulting) had not heard about it, and far less were actually using it. This really surprises me, since NPS integrates like a charm with Agile, e.g. within product development via Scrum.

    In this session I'll explain the basics of NPS, i.e. promoters and detractors, satisfied and delighted customers, bad profits (how to deal with bad feedback?) and good profits, and why and how to measure these. Several stories from companies like Apple Retail, Zappos, Southwest Airlines, and others will help to make my point. I’ll further show why NPS is a very good fit with Agile regarding products, employees, and personal performance. Dos and Don’ts regarding NPS (also from personal experience) will close this session. Related to the Don'ts, I also cover some of the negative critiques out there.

  • Liked Victoria Schiffer
    keyboard_arrow_down

    Victoria Schiffer - Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    Agile Coach
    SEEK
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    I love being around awesome people, who build great products customers desire. 
    I love learning from and together with these amazing minds. 
    I love creating the right environment for teams to flourish. 
    I love change, and learning from new experiences. 
    I love working in Agile environments.

    How about you? 
    I bet there are some elements of this list why you're in Agile, too. And you can probably add even more elements to it.

    The Agile Manifesto states amongst others individuals and interactions, customer collaboration and responding to change.

    In our everyday life doing Agile we already respect these aspects in many ways. 
    But do we practice what we preach as best we can?

    I'd like to challenge your current way of thinking about people and processes. 
    I'd like to challenge you to focus on you, before you focus on others. 
    I'd like to challenge your current way of reflecting. 
    I'd like to inspire you to go different ways. 
    I'd like to inspire you to inspire others.

    In Agile we're already good in improving our processes and creating well performing teams and hence building the right things in the right way. And in the Agile Manifesto's communication and collaboration piece we can even get better.
    "You have not yet reached the limit of what you're capable of!" means we can always further improve. And we do follow this idea in our Agile processes, too, through continuous feedback (Retrospectives) and improvement.

    And why not take it even further? Why not go "Beyond Agile"?!

    Here's where aspects of Life Coaching come in handy: through also understanding and improving ourselves (how do we interact with people due to how we perceive our environment) we will even further improve communication and collaboration.

    Life Coaches believe our clients know the answer. And even if Agile Coaching is slightly different than Life Coaching, I see it as very relevant in Agile Coaching, too. If we apply this in Agile, instead of giving our clients (team, colleagues) the answers, asking them powerful questions to help them be more aware of what's happening at the moment, they will find their answer for it and will have a much better commitment to making the change for themselves, their teams and the company. It's not for us to TELL them what to do, but to ASK them what's going on for themselves. Here's where I see a huge chance for improvement.

    In my session I give lots of examples on how to link Life Coaching ideas to our Agile work environments. I've given the session at LAST Conference Melbourne and at the Agile Coaching Circles Meetup Melbourne. The audience was engaged and the attendees were very happy about having some new ideas on how to improve their daily work life.

    Come along to be inspired by Life Coaching and thus to benefit our Agile Thinking!

  • Liked Lynne Cazaly
    keyboard_arrow_down

    Lynne Cazaly - The Girl with the Chisel Tip Marker

    Lynne Cazaly
    Lynne Cazaly
    Owner
    Lynne Cazaly
    schedule 4 years ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    One of the quickest ways to achieve greater buy-in, clearer communication and higher levels of engagement with team members, stakeholders, sponsors and business units is to get "visual agility". Using cards, stories, post it notes, visual charts, maps, models, metaphors - and most of all, some hand crafted "drawn-in-the-moment" visuals learn some engaging ways to facilitate with visuals in an Agile world. 

    Many people speak about 'making work visible' - showing progress, visualising solutions, scoping out possibilities - having visual agility gives you the skills to step into any role at a moment's notice and help bring clarity to the problem, quicker. This can apply to individual thinking and brainstorming, or group situations when you're presenting your idea or you're working with the group to create a solution. 

    Lynne Cazaly is a communications specialist and master facilitator. Lynne provides clarity to project complexity through workshops, training and visual strategy. Lynne trains, facilitates, speaks and coaches on visual facilitation, visual thinking and other engaging tools for project people, to help boost buy-in, collaboration and engagement.

    Lynne Cazaly is the author of the book 'Visual Mojo - how to capture thinking, convey information and collaborate using visuals'. 

    http://www.lynnecazaly.com.au/visual-mojo-the-book-lynne-caz/

    Included in this session is 30 icons to use straight away which Lynne calls 'Quick Pics'.

    Lynne recently ran the session again in New Zealand at an Agile Wellington Meetup - read their comments here

  • Liked Ram Srinivasan
    keyboard_arrow_down

    Ram Srinivasan - The Conflict Paradox

    90 mins
    Workshop
    Intermediate

    It is not a question of if a team is going to have a conflict; it is a question of when. Equipping them to deal with conflict is more than creating agreements or having a good facilitator. We look at a conflict model that focuses on dynamics of conflict by understanding- 1. Cognitive skills:self-awareness about triggers, hot spots, emotions,behaviors. 2. Emotional skills:reading emotions, body language, balancing emotions, using curiosity 3. Behavioral skills:understanding others’ perspectives and needs, avoiding 8 destructive behaviors, embracing 8 constructive behavior. In an organizational setting, it is important to understand the source (culture, interdependence, incompatibility, personality, power, etc.) and types of conflict (cognitive vs. affective). Creating awareness about conflict processes, retaliatory cycles and building a conflict profile can empower teams engage in constructive disagreements. 

  • Liked Phil Abernathy
    keyboard_arrow_down

    Phil Abernathy - The Sixth Force

    45 mins
    Talk
    Intermediate

    Over the last 2 years, in small pockets all over the world, people have been experimenting with the use of Agile and Lean in formulating and executing corporate strategy.

    The finding will astound you and lay the foundations for what may become the next wave of ‘Agilean’ transformations, thus paving the way for vertically transformed ‘Agilean’ organisations that deliver outstanding profitability.

    The ‘Lean Startup’ mentality or ‘Management 3.0’ are tips of the iceberg in recent strategic thinking.

    This talk draws on experience and real life examples to outline how Agile and Lean, and not just Porter’s 5 forces, can be used effectively to not only formulate and execute corporate strategy but also to enable transformation throughout the organisation.

  • Liked Fiona Mullen
    keyboard_arrow_down

    Fiona Mullen - Agile - An Australian Journey of Cultural Change

    45 mins
    Talk
    Beginner

    How did one of Australia's leading financial services organisation become the biggest Agile transformation story in the Southern hemisphere and what did we learn?

    The Suncorp Group leads in general insurance, banking, life insurance, superannuation and investment brands within Australia and New Zealand. The Group has 16,000 employees and relationships with nine million customers. It is a Top 20 ASX listed company with over $93 billion in assets.

    In 2007, we embarked on our Agile journey of cultural change. In this talk we will cover the strategy taken, the roadblocks we came across, the mistakes we made and the achievements along the way.

    You will learn how to tackle an Agile transformation, what to do and what NOT to do, where to start and what to expect and most of all what impact it will have, both negative and positive.

    Today Suncorp are seen as market leaders in Agile and are known globally for the Agile Academy http://www.agileacademy.com.au/agile/ which was designed for both staff and also the external market.

    The role of the Agile PMO, how to get infrastructure to work Agile, what about all those legal challenges, the cultural differences and the resistance to change? These are some of the learning we will share.

    There were challenges and successes and in this honest Aussie presentation will share with you both the highs and the lows.

  • Liked Herry Wiputra
    keyboard_arrow_down

    Herry Wiputra - Crossing the T's and Dotting the I's

    20 mins
    Experience Report
    Intermediate

    The term "cross functional team" has been made popular by the Agile movement. In cross functional team, we put people with different roles to work together for a common goal/purpose.

    I have seen this worked really well in many agile teams. People are no longer on silo and everyone have better understanding what each other's role is and consequently, what each other do. This leads to better self organising within the team.

    However, I strongly believe we can take this concept to the new level. The concept of cross functional team should be extended to not just the team but also to the individuals within the team. Scott Ambler wrote an essay on "Generalising Specialist". The term T-shaped developer was introduced by Mary and Tom Poppendieck in her famous book "Lean Software Development". By nature, people don't like to get out of their comfort zone, hence the tendency to keep working in area that they are familiar with. When leaders can create an environment where everyone is encouraged to learn, grow and make mistakes, amazing things can happen.

    In my experience leading teams, I have witnessed many transformations that enabled individuals to go beyond their traditional role, such as a manual QA assuming Scrum Master role, a BA doing deployment, a developer doing QA for a story, etc. Not only this enablement help develop the individuals to widen their horizon and skillset, it also helped the productivity of the team through better collaboration. When a team reach this stage, we no longer have problems such as "The QA has nothing to do because there are no stories to test", "The developers have nothing to do because the cannot keep up", "The deployment took longer than expected because the Ops person was not aware of the special configuration".

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Prasanna Vaste - Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    Business Analyst
    Thoughtworks
    schedule 4 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Allen Rutzen
    keyboard_arrow_down

    Allen Rutzen / Sunil Roy - Nokia Maps Agile Journey.....(Agile Transformation, Scaling and Overcoming Challenges)

    45 mins
    Talk
    Intermediate

    We (at Nokia Maps Division) began our Agile Journey in 2009, with a Top Down approach for Agile Transformation. The formation of an Agile Working Group (with members having Agile experience behind them) at two major sites was instrumental in shaping the transformation and scaling and also overcoming the challenges from time to time.

    The challenges were huge, but our spirit was bigger, and the high level strategy was decided. Interestingly, the Agile Working Group itself ran the whole Transformation and Scaling program using Agile values and Scrum frame work. Scrum was also used as the preferred framework for the agile projects (after success in our pilots), except where Scrum would not work. Kanban or hybrid methods were used in those few teams.

    What were the challenges faced, and how did we overcome them? What values helped us in our transformation journey?

    How did we migrate to the Scaling phase? What helped us in scaling and stabilizing?

    Can we rest easy now? Of course not!

    What are the next steps? And of course, the challenges ahead?

    Let us share our Nokia Agile journey with you, and help you all be successful too, in your Agile journey!

  • Liked Naresh Jain
    keyboard_arrow_down

    Naresh Jain - SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 4 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Bernd Schiffer
    keyboard_arrow_down

    Bernd Schiffer - Inspire Management! From Status Quo to Awesome

    45 mins
    Talk
    Intermediate

    One of the most rewarding change opportunities for organization to create awesome workplaces exists by being innovative at the management level. Forget step-by-step explanations of management practices (you can’t copy culture!); the key to address the management level - i.e. to foster innovations at this level - is by inspirations. In order to get an awesome workplace, you have to see awesome workplaces. There are plenty of ways to inspire people, but this opportunity is often wasted during the introduction of Scrum and Kanban methods, or never reflected upon afterwards.

    In this session, I will show you several aspects of awesome workplaces. A constantly growing container for inspiring management are the Agile Management Innovations (AMI). AMIs are practices for management which lead to democracy, fairness, decentralisation, dialogue, and lot of other positive effects. These effects lead to awesome workplaces, where people are truly motivated. The idea behind inspiration is to foster creativity and innovation through a changed environment. Management practices can't be just applied; 50% of management practices depend upon the organisation's culture. That's why we call them AMInnovations.

    If you experiment with AMIs, you'll get from status quo to awesome (that is of course only when you're status quo is not already awesomeness).

    I’ll introduce the concept of AMI as well as plenty of real world examples. The goal is to inspire you twofold: I will inspire you in this session to experiment with AMIs, and AMIs will inspire the people within your organisation to achieve a better workplace.

  • Liked Neil Killick
    keyboard_arrow_down

    Neil Killick - The Guessing Game - Alternatives to Agile Estimation

    Neil Killick
    Neil Killick
    Lead Agile Coach
    MYOB
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Agile promotes empiricism and change, yet many practitioners continue to scope out and estimate delivery times and costs for software products and projects.

    Defenders of the art of estimation claim that we need to estimate software projects in order to answer common business and customer questions such as:

    • Should we go ahead with this project? (go/no-go)
    • How much will it cost? (bottom line)
    • When will it be done? (predictability)
    • Should we do project B instead of A? (prioritisation)

    This session challenges participants to flip these questions on their heads and seek alternatives to estimation rituals. It covers the many risks inherent with an estimation culture and demonstrates real, practical alternatives, both at the portfolio and the sprint level.

  • Liked Bhuwan Lodha
    keyboard_arrow_down

    Bhuwan Lodha - Building a Team Backlog: The Power of Retrospectives

    Bhuwan Lodha
    Bhuwan Lodha
    VP - Digital
    McKinsey & Company
    schedule 4 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

  • Liked Jayaprakash Puttaswamy
    keyboard_arrow_down

    Jayaprakash Puttaswamy - Agile Transformation Strategies - Insight from software & non-software world

    90 mins
    Workshop
    Intermediate

    Large-scale agile transformation across organization is not only challenging to implement, but also relies heavily on strategic leadership skills of the organization leaders who drive it. In this workshop, apart from me sharing my experience of driving large-scale agile transformations from an agile coach and strategist’s point of view, participants would be encouraged to share their valueable insight as well through agile innovation games. The workshop attempts to unwind some of the intricacies of challenges involved in enterprise agile transformation and it would be presented at a big-picture level, connecting the deeper insights to agile transformation strategies. The workshop would be organized around "Agile transformation challenges" and "Strategies for effective agile transformation". Strategies described focus around Adoption, Delivery and Scaling aspects of the transformation.

  • Liked Prerna Kale
    keyboard_arrow_down

    Prerna Kale - Cent Cent Business Value! A Sneak Peek at sprints from evolving design/UI, getting right priorities to delivering $$

    Prerna Kale
    Prerna Kale
    Senior Product Owner
    TCS
    schedule 4 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

     

    We want to share experience of working on a complex project, with deadlines set upfront and all players distributed. Perhaps argued as a complex combination to have but yet we were right there, on time enabling the new tool there. Reporting systems often have evaluation cycle that have imperative timelines to start and freeze, hence working for a huge system was not easy. Right agilist mindset with right agile practices helped us meet this. As a Product owner I jostled with eight experts using one system with some variation for their own service lines. We want to show how we leveraged the benefits of distributed teams balanced the challenges, kept the UI flexible enough to accommodate 8 expert reviews, and how our evolving architecture designed a system that had the most used and important features for the users to try hands on..

    Introspecting and sharing how we ensured Cent Cent business Value:

    - Kick off the project with eight stakeholders that got the ball rolling
    - Identifying the 30 % that was core to the business
    - Inspecting, and adapting to constant changes with modular designs
    - Getting stakeholder agree on priorities
    - Release Backlog with stories and design with validated acceptance criteria
    - Managing challenges and ensuring meeting needs seamlessly with truly distributed teams (Distributed PO/Designer/Architect/ Team/ Stakeholders)

    How important is it to dig the core 20-30% in projects with deadline upfront and ways to do that.. Prioritization techniques that enabled mutual agreement on the needs. Backlog with designs that reduced the development time. How work effectively with distributed teams, by building trust, keeping motivation and sharing the definition of done- yes we lived it and did it! We want the audience to explore it all with us and be open to take up and successfully meet the projects with distributed agile teams and tight deadlines yet agile :)

  • Liked Pradeepa Narayanaswamy
    keyboard_arrow_down

    Pradeepa Narayanaswamy - Agile Testing- What is my success mantra??

    45 mins
    Talk
    Beginner

    As more and more organizations are transitioning to agile, it’s inevitable that Agile testing is not just a concept any more. It is also not just about placing a tester in every team. What is so radically different now? How to be successful at agile testing? How to be an effective cross-functional team that embeds and honors all specialties including testing?

    In this presentation, I am going to share my teams’ success with Agile testing and how we incorporated these 3 aspects – people, process and tools/techniques. This talk will benefit any members in an organization who has a stake in the product quality. It is also highly beneficial for those agile testers (from aspiring to veteran) to understand the 3 main aspects as it relates to testing and why we need to embrace- not just one, not two, but all these 3 aspects to be successful in Agile testing. 

     

     

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Vibhu Srinivasan - Coding with Geeks- De Code the secrets behind TDD, BDD and ATDD

    90 mins
    Tutorial
    Intermediate

    This session is a coding sessiont that takes a problem and shows clearly what is the difference between TDD, ATDD and BDD. Ths session uses code for the server layer as well as UI layer.

    This session is not for you if you do not code. If you do code, please bring your laptop as we delve into the details of all these styles of programming techniques.

    We will rotate between ATTD, TDD and BDD periodically and show it at use in different layers. This session will be using Java , Rails, Scala and C# together so that you can see how you can benefit do these techniques even when coding in different languages.

    We look at common pitfalls and wrong beliefs that programmers have when it comes to these concepts

    This session is purely keyboard and you will have to bring a laptop.

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Vibhu Srinivasan - Working at a lean startup

    20 mins
    Experience Report
    Beginner

    I have had the oppurtunity to build and be part of a few successful and failed startups. One such succesful startup was my association with a startup called Evri.com. I have also consulted as a developer and coach for a gaming company called BigFishGames which went to become a largely succesful gaming company making one game a day today. 

    In this session I would like to tell the story of what happened at Evri and Big Fishgames that made them succesful. 

    This is a lessons learned, observatiosn shared being part of this startup as a developer. This session also looks at what makes a good product. Is product creation a pure idea of a bunch of geeks working together or something more than that. 

     

    Come see and learn

  • Liked Shrawan Gaur
    keyboard_arrow_down

    Shrawan Gaur - Learn from Mistakes, Retain Your Strong Holds: Sprint Retro: Do As WE Do at John Deere

    45 mins
    Talk
    Beginner

    As the 12th Agile Principle states : "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.", it is quite easy to understand the importance of continuous evolvement which involves retaining learning and corrective actions.

    John Deere has started its Agile journey in year 2010 and since then has gone through various phases of transformation. Scrum teams has learnt alot and are continuously learning. Retrospection is one of very important scrum ceremony which paves path for team to advance in right direction.

    Here, I will demonstrate some retro techinques and its applications according to sprint work.