• Liked Giovanni Asproni
    keyboard_arrow_down

    Methodology Patterns: a Different Approach to Create a Methodology for Your Project

    Giovanni Asproni
    Giovanni Asproni
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Advanced

    In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

    In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

    The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

    Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

    Our main question was: As mobile app developers, how should we architect/design our apps for CD?

    We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

    If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

  • Liked Victoria Schiffer
    keyboard_arrow_down

    Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    schedule 3 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 Bernd Schiffer
    keyboard_arrow_down

    Net Promoter System for Agile Companies

    Bernd Schiffer
    Bernd Schiffer
    schedule 3 years ago
    Sold Out!
    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 Nikhil Joshi
    keyboard_arrow_down

    Build - Measure - Learn : Without spending a fortune

    Nikhil Joshi
    Nikhil Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Liked Tathagat Varma
    keyboard_arrow_down

    Agile, Management 3.0, Holacracy...what next?

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Pesentation deck is now available at http://www.slideshare.net/Managewell/what-next-31791295

    Modern management methods are still based on the then seminal work by Henri Fayol some 200 years back, followed by Frederick Taylor's work some 100 years back! Sadly, those models were predominantly based on industrial work, and don't really work that well in knowledge industry and today's sociological dynamics at workplace. Classical Agile methods codify several people practices that allow for a self-organizing team to evolve, but doesn't offer a lot of guidance on how to develop and groom leadership for agile organizations beyond a software team. Management 3.0 takes this issue further and develops it into a separate discipline altogether. On similar lines, Holacracy seeks to create social technology for purposeful organizations, though not specially targeting software organizations. So, the issue of leadership still continues to be unresolved and rather left to pave its way on its own. Unfortunately, when we want to achieve true end-to-end agility, it is not enough for software teams to be charging at top speeds but leadership not evenly matched to support them well in their endeavors. We clearly have a problem at hand...

    In this talk, we will study how the role of leadership has evolved and what does it look like for agile organizations at present. Many agile methods take an extreme view that limit leadership to team-level collective ownership of leadership. However, that might not be enough because of various reasons. In any non-trivial organization, whether a software organizations or any modern business employing software for business advantage, the reality is that organization units beyond a plain-vanilla software teams do exist. So, how does one go about grooming their top talent for playing an effective part in this process?

    Finally, we will also try to take a shot at some of evolving paradigms. For example, all these management thoughts are still based on the kind of outdated premise that an organization is based on 'boundaries' of operations. However, already we see that model being broken down, and the future teams look more like boundaryless entities bound with nothing but a unifying purpose that brings a bunch of volunteers together for a period of time. If our success increasing depends on such teams being able to effectively self-manage themselves, what role does leadership have to play in it, and are we getting ready for it? 

  • Elinor Slomba
    Elinor Slomba
    schedule 3 years ago
    Sold Out!
    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 Todd Little
    keyboard_arrow_down

    Risky Business: Real Options for Software Development

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Software projects are known to have challenges with estimation, uncertainty, risk, and commitment - and the most valuable projects often carry the most risk. Other industries also encounter risk and generate value by understanding and managing that risk effectively. Todd Little explores techniques used in a number of risky businesses - product development, oil and gas exploration, investment banking, medicine, weather forecasting, and gambling - and shares what those industries have done to manage uncertainty.

  • Liked Jez Humble
    keyboard_arrow_down

    Secrets of Growing an Innovation Culture

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The fundamental problem with software methodologies is that none of them work. What's decisive is not which one you adopt, but what you do to continue to innovate around your processes. In this wide-ranging talk, I'll discuss why command-and-control leads to risk management theatre, and why this makes things riskier and more painful. I'll present the essence of innovation culture, how it works at scale, and present some tools (including the Improvement Kata) to help you think differently about how to grow great software.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Automate across Platform, OS, Technologies with TaaS

    Anand Bagmar
    Anand Bagmar
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Advanced

    "TaaS" is an open-source product that allows you do achieve the "correct" way of doing integration testing across a variety of products via Test Automation.

    Typically in organizations, there are multiple projects / products. Many organizations like to have a common Test Automation solution across these products in an effort to standardize the framework.

    However, this is not a good idea! Each product should be tested using the tools and technologies that are "right" for it. Yet - these different products talk with each other and you need to test the integration between them in an automated way.

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    schedule 3 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 Ram Srinivasan
    keyboard_arrow_down

    The Conflict Paradox

    Ram Srinivasan
    Ram Srinivasan
    schedule 3 years ago
    Sold Out!
    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 Vibhor Agarwal
    keyboard_arrow_down

    Microsoft Visual Studio's Journey to Continuous Delivery

    Vibhor Agarwal
    Vibhor Agarwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Microsoft Visual Studio is now releasing at a much faster pace and the Team Foundation Service has  a deployment every sprint. We adopted agile practices across the board and made significant improvements to engineering processes and systems down the way. What are the impediments to agile and how you overcome them. How do you reimagine the role of developers and testers in this new era. What kind of tools do you need to make this transition a success for your team ?

    Come and learn what it takes to adopt modern processes to ship complex products like Visual Studio with engineering teams spread across the globe to ship at cloud cadence. 

  • Liked Phil Abernathy
    keyboard_arrow_down

    The Sixth Force

    Phil Abernathy
    Phil Abernathy
    schedule 3 years ago
    Sold Out!
    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 Lyssa Adkins
    keyboard_arrow_down

    Hiring (or Growing) the Right Agile Coach

    Lyssa Adkins
    Lyssa Adkins
    Michael Spayd
    Michael Spayd
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    There are as many types of agile coaches out there as there are flavors of ice cream.  And, their levels of leadership maturity and skill can vary just as widely.  It can leave one fretting, "What am I really getting when I bring in an agile coach?  And, how do I 'grow' my own?"  In fact, what are the "must have" skills of an agile coach and how can you tell if your coach has them?  The Agile Coach Competency Framework is one big clue to answering these questions. Over the past two years, this framework has guided the development of hundreds of agile coaches. Agile managers and champions also use it to obtain "truth in advertising" to hire the right coach at the right time.  We will explore this framework and provide lightening-talk-style case studies that showcase how it has been used in the real world.  You'll leave with ideas and actions to help you become a more savvy purveyor (and/or developer) of agile coaches.

  • Liked Roy Nuriel
    keyboard_arrow_down

    The Quality Assurance Journey - From Waterfall to Continuous Delivery

    Roy Nuriel
    Roy Nuriel
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

    In this session I will share how we made the shift, while focusing on the change in our quality process.

    As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

    We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

    Here are some of the dilemmas we faced:

    -          What are the differences between "Dev Tester" and "QA Engineer"?

    -          How can we measure quality in 2-week sprints?

    -          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

    -          When and how should load testing be performed?

    -          Automated v. manual testing

    -          What testing should be part of the CI process?

    -          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

    We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

  • Dave Thomas
    Dave Thomas
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Advanced

    In 2002, Secretary of Defense Donald Rumsfeld introduced us to the concepts of known knowns, known unknowns, and unknown unknowns. But he left out Unknown Knowns, things that we know without knowing it. And it turns out that these Unknown Knowns are actually the biggest category of knowledge - tacit knowledge.


    As developers, we work with knowledge: knowledge of the problem domain, knowledge of our tools, knowledge of our techniques, and knowledge of each other. So getting good at accumulating tacit knowledge is important.

    This talk will look at how we are poorly served by most of the current ways we are taught to be better developers. Can we do better? Only if we stop talking and start showing. Let's see why.

  • Liked Venkat Kandaswamy
    keyboard_arrow_down

    Applying Agile to a Bootstrapped Startup

    Venkat Kandaswamy
    Venkat Kandaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The default state of a Start up is Failure - Chris Dixon. On 18-Sep-2008, on the day Lehman Brothers collapsed, I started developing a prototype ( which later became ApartmentADDA.com ), with an unclear picture of the problem definition, not much access to the target Users and zero funding.

    Having experienced Agile as a Developer at ThoughtWorks, I tried applying some of the agile concepts. Found it a fabulous fit - true to its promise of light in the darkness of uncertainty and imprecise problem statements.

    In this talk I will take you through my Start up Journey - the first 5 years when we were Bootstrapped - how we were able to nail the Problem Definition and find the Product Market fit and how we overcame severe resource constraints - not only in Product Development, but in other functions like Sales, Marketing and Support.

    I will make a case on how applying Agile prudently to a Bootstrapped Start up can change the Default State of a Startup - which is Failure - to that of a Success.

  • Liked Todd Little
    keyboard_arrow_down

    Risky Business: Real Options for Software Development

    Todd Little
    Todd Little
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Software projects are known to have challenges with estimation, uncertainty, risk, and commitment - and the most valuable projects often carry the most risk. Other industries also encounter risk and generate value by understanding and managing that risk effectively. Todd Little explores techniques used in a number of risky businesses - product development, oil and gas exploration, investment banking, medicine, weather forecasting, and gambling - and shares what those industries have done to manage uncertainty.

  • Liked Jez Humble
    keyboard_arrow_down

    Secrets of Growing an Innovation Culture

    Jez Humble
    Jez Humble
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The fundamental problem with software methodologies is that none of them work. What's decisive is not which one you adopt, but what you do to continue to innovate around your processes. In this wide-ranging talk, I'll discuss why command-and-control leads to risk management theatre, and why this makes things riskier and more painful. I'll present the essence of innovation culture, how it works at scale, and present some tools (including the Improvement Kata) to help you think differently about how to grow great software.

  • Elinor Slomba
    Elinor Slomba
    schedule 3 years ago
    Sold Out!
    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

    Net Promoter System for Agile Companies

    Bernd Schiffer
    Bernd Schiffer
    schedule 3 years ago
    Sold Out!
    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

    Agile Coaching? Sure thing! What about Life Coaching in Agile Thinking?

    Victoria Schiffer
    Victoria Schiffer
    schedule 3 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 Giovanni Asproni
    keyboard_arrow_down

    Methodology Patterns: a Different Approach to Create a Methodology for Your Project

    Giovanni Asproni
    Giovanni Asproni
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Advanced

    In the software world we have been looking for “The Methodology” to solve our software development sorrows for quite a while. We started with Waterfall, then Spiral, Evo, RUP and, more recently with XP, Scrum, Kanban, DAD, SAFe (there are many others, but, their impact, so far, has been limited).

    In this tutorial, I'll show why this search for the holy grail is bound to fail--each methodology has strenghts and weaknesses that make it suitable only in some contexts--and I'll describe a different approach based on patterns and pattern languages, that teams can use to create their own methodologies to suit their specific needs, which, in my experience, has a higher chance of success. 

    The approach is based on the observation that all the practices used in all modern methodologies--e.g., user stories, use cases, team self organization, TDD, unit testing, acceptance testing, continuous integration, iterative and incremental development, etc.--come from the same set. Different methodologies just mix and match them differently. All those practices can (and many have already been) described as patterns whose relationships with each other form a set of pattern languages.

  • Liked Lyssa Adkins
    keyboard_arrow_down

    Hiring (or Growing) the Right Agile Coach

    Lyssa Adkins
    Lyssa Adkins
    Michael Spayd
    Michael Spayd
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    There are as many types of agile coaches out there as there are flavors of ice cream.  And, their levels of leadership maturity and skill can vary just as widely.  It can leave one fretting, "What am I really getting when I bring in an agile coach?  And, how do I 'grow' my own?"  In fact, what are the "must have" skills of an agile coach and how can you tell if your coach has them?  The Agile Coach Competency Framework is one big clue to answering these questions. Over the past two years, this framework has guided the development of hundreds of agile coaches. Agile managers and champions also use it to obtain "truth in advertising" to hire the right coach at the right time.  We will explore this framework and provide lightening-talk-style case studies that showcase how it has been used in the real world.  You'll leave with ideas and actions to help you become a more savvy purveyor (and/or developer) of agile coaches.

  • Liked Bernd Schiffer
    keyboard_arrow_down

    Inspire Management! From Status Quo to Awesome

    Bernd Schiffer
    Bernd Schiffer
    schedule 3 years ago
    Sold Out!
    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 Ram Srinivasan
    keyboard_arrow_down

    The Conflict Paradox

    Ram Srinivasan
    Ram Srinivasan
    schedule 3 years ago
    Sold Out!
    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 Vibhor Agarwal
    keyboard_arrow_down

    Microsoft Visual Studio's Journey to Continuous Delivery

    Vibhor Agarwal
    Vibhor Agarwal
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Microsoft Visual Studio is now releasing at a much faster pace and the Team Foundation Service has  a deployment every sprint. We adopted agile practices across the board and made significant improvements to engineering processes and systems down the way. What are the impediments to agile and how you overcome them. How do you reimagine the role of developers and testers in this new era. What kind of tools do you need to make this transition a success for your team ?

    Come and learn what it takes to adopt modern processes to ship complex products like Visual Studio with engineering teams spread across the globe to ship at cloud cadence. 

  • Liked Phil Abernathy
    keyboard_arrow_down

    The Sixth Force

    Phil Abernathy
    Phil Abernathy
    schedule 3 years ago
    Sold Out!
    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.

  • Dave Thomas
    Dave Thomas
    schedule 3 years ago
    Sold Out!
    60 mins
    Keynote
    Advanced

    In 2002, Secretary of Defense Donald Rumsfeld introduced us to the concepts of known knowns, known unknowns, and unknown unknowns. But he left out Unknown Knowns, things that we know without knowing it. And it turns out that these Unknown Knowns are actually the biggest category of knowledge - tacit knowledge.


    As developers, we work with knowledge: knowledge of the problem domain, knowledge of our tools, knowledge of our techniques, and knowledge of each other. So getting good at accumulating tacit knowledge is important.

    This talk will look at how we are poorly served by most of the current ways we are taught to be better developers. Can we do better? Only if we stop talking and start showing. Let's see why.

  • Liked Venkat Kandaswamy
    keyboard_arrow_down

    Applying Agile to a Bootstrapped Startup

    Venkat Kandaswamy
    Venkat Kandaswamy
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The default state of a Start up is Failure - Chris Dixon. On 18-Sep-2008, on the day Lehman Brothers collapsed, I started developing a prototype ( which later became ApartmentADDA.com ), with an unclear picture of the problem definition, not much access to the target Users and zero funding.

    Having experienced Agile as a Developer at ThoughtWorks, I tried applying some of the agile concepts. Found it a fabulous fit - true to its promise of light in the darkness of uncertainty and imprecise problem statements.

    In this talk I will take you through my Start up Journey - the first 5 years when we were Bootstrapped - how we were able to nail the Problem Definition and find the Product Market fit and how we overcame severe resource constraints - not only in Product Development, but in other functions like Sales, Marketing and Support.

    I will make a case on how applying Agile prudently to a Bootstrapped Start up can change the Default State of a Startup - which is Failure - to that of a Success.

  • Bimlesh Gundurao
    Bimlesh Gundurao
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Transforming a Business to be Agile involves a lot of moving parts. Being Agile not only means delivering high quality software, but ability to respond to changing Customers Needs/Markets/Competitors/Stakeholders and more. Fundamental to this change is "People" within the organization. Keeping “People Over Process” at the center its important  to facilitate the People in the organization to be fully successful. So how do we ensure they are successful? How does goal setting change? How does measurement of these goals change? Focus on Organization adoption to Agile largely has been limited to Engineering function. But how has the HR process changed to facilitate this transformation to be truly successful?

    In this session will look to bring in some of the best practices that are followed in the organizations through a Mix of Case Study and Research across Product and IT Services Organizations.

  • Liked Roy Nuriel
    keyboard_arrow_down

    The Quality Assurance Journey - From Waterfall to Continuous Delivery

    Roy Nuriel
    Roy Nuriel
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    In the past several years we have seen more and more organization taking the decision and moving their development divisions to adopt Agile methodology. In most cases the change starts with a POC of a new and – in most cases – small project that validates the ability of the organization to make the shift to Agile. In many cases the development team takes the lead: changing the process, moving to unified teams, selecting which Agile practice to adopt, etc.

    In this session I will share how we made the shift, while focusing on the change in our quality process.

    As an R&D group that develops an Agile solution (HP Agile Manager), we wanted to get it right. We changed the way in which we develop software from waterfall to Agile, and built a process to support the teams in a complex and large enterprise. While previously we were accustomed to delivering releases in 1-2 year cycles, we now operate within a SaaS model where we update our production environment on a weekly basis. 

    We have experimented with the same process that our customers are going through and, as a result, we adapted the way our QA engineers work. In accordance with their new role, we gave them a new title – Dev Testers.

    Here are some of the dilemmas we faced:

    -          What are the differences between "Dev Tester" and "QA Engineer"?

    -          How can we measure quality in 2-week sprints?

    -          What needs to change when testing a SaaS solution that is delivered on a weekly basis?

    -          When and how should load testing be performed?

    -          Automated v. manual testing

    -          What testing should be part of the CI process?

    -          How do offshore Dev Testers take part in our Agile practices (e.g. daily meetings)?

    We dealt with all of these questions, and I would like to share the lessons we learned, our conclusions, and some of the challenges that we still face.

  • Liked Archana Joshi
    keyboard_arrow_down

    Applying Agile Principles in Primary School Education: An experience

    Archana Joshi
    Archana Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    An important issue that has plagued the Indian sub-continent is that of education and more importantly primary education. Since past few months, my weekends are usually occupied in teaching English classes to underprivileged children from 5th grade at a government primary school. As an Agile coach and a practitioner I was drawn towards unifying the concepts of Agile to help increase the quality of education.

     

    As a teacher, I was given a set of high level goal by the school administrator that needs to be accomplished every quarter. My goals for the first quarter were :

    • > Kids should be able to identify basic words
    • > Form short sentences.
    • > Converse reasonably in English

     

    I started with the traditional chalk and blackboard style of teaching focusing on the spellings, grammar, sentences, reading and so on. In initial few sessions, I quickly realized that it took too long for the kids to understand and so was not yielding the desired results. Some of the problems were like

    • > Too much focus on semantics and grammar
    • > Kids not opening up in the class room
    • > Only able to read words but not talk or frame sentences

     

    This is where I had to reflect and consider course correction in my style of teaching and Agile came to my rescue. This is a talk which highlights how Agile techniques were applied in teaching kids effectively.

     

     

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    Leadership Agility - Organizational Agility - winning agile transformations

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    "Agile doesn't work for me, my team and my organization" have you heard or experienced this, if so this presentation gives you an insight about how leadership is responsible for driving the transformation. I shall focus on the leadership agility levels and organizational agility parameters, also I would discuss the aspects that connect the leadership style and culture. Over 90% of leaders operate at an heroic leadership level as experts and achievers, this traditional approach limits the organizational agility, innovation and productivity. Leadership agility requires a paradigm shift from a world of competition and duality to collaboration and unity. Organizational agility is a journey, learn how being a catalyst leader helps achieving organizational agility.

    “Leadership bring culture to organization and culture builds leadership agility”

  • Liked Khaarthigha S
    keyboard_arrow_down

    Product Visioning during Inception

    Khaarthigha S
    Khaarthigha S
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    One struggle that we face in service sector in kickstarting new projects is understanding the vision of the product that business envisions or problems that business face. Especially when consulting in a wider vertical ( Retail, Medical, Data Analytics, etc...) , we constantly see a gap initially as to what the business vision for in a product that they would like to build and that is exactly what we want in helping Clients with our solution. As this understanding gets us to think innvoatively to solve the problem statement and ultimately this gets pictured in proposals and then projects. This consists of many subsets which is where we would like to see the features of the product that we build. This session focuses on how to use Product Box/ Press Note exercises to clearly get the vision in Product Owner/Program Mangager or whomsoever from Business (Client) to get the clear understanding of their vision in the product that they wish to see. This helps us to get into the insight of all the features and this excercise gets out everything in everybody's mind at ease. Also it is a good team exercise, builds good relation ship with the Client team too. 

  • Liked Khaarthigha S
    keyboard_arrow_down

    Agile & Consulting on Social Impact Projects

    Khaarthigha S
    Khaarthigha S
    schedule 3 years ago
    Sold Out!
    45 mins
    Others
    Intermediate

    We are in living in the days where global giants(UNICEF, WHO, Bill Gates Foundation,...) invest in the social sector which now is the hitlist in the record of attraction.  Information technology required for the upliftment of social sector via lot of aggressive themes on Financial Inclusion, HealthCare & Medical Inclusion, Targetting MDGs(Millenium Development Goals), etc... The session is focussed on portraying one such instance and how agile with lean methodology helped in the accomplishments of major contribution of IT in social space. The session will also have a greater latitude on how analysis and the breakdown of complex problem acheived more easier in agile way driving more directed at the outcomes and not just at the outputs. 

  • Liked Anushya Prasad
    keyboard_arrow_down

    Lean Kitchen

    Anushya Prasad
    Anushya Prasad
    schedule 3 years ago
    Sold Out!
    20 mins
    Case Study
    Beginner

    Ever watched a pair of cooks on Master Chef working in teams, an open kitchen in a restaurant or Gordon Ramsay yelling across the kitchen at his team of chefs?

    Ring a bell? Doesn't it remind you of your project team? Or if you're a foodie like me, of the similarities between a software project, your team and a Gourmet kitchen? Is there something we can learn from them?

    This talk is an attempt to draw such a comparison highlighting how our teams and a bunch of chefs in a restaurant kitchen function to whip up something so delectable that our customers want to come back for seconds. 

  • Liked Tathagat Varma
    keyboard_arrow_down

    Agile, Management 3.0, Holacracy...what next?

    Tathagat Varma
    Tathagat Varma
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Advanced

    Pesentation deck is now available at http://www.slideshare.net/Managewell/what-next-31791295

    Modern management methods are still based on the then seminal work by Henri Fayol some 200 years back, followed by Frederick Taylor's work some 100 years back! Sadly, those models were predominantly based on industrial work, and don't really work that well in knowledge industry and today's sociological dynamics at workplace. Classical Agile methods codify several people practices that allow for a self-organizing team to evolve, but doesn't offer a lot of guidance on how to develop and groom leadership for agile organizations beyond a software team. Management 3.0 takes this issue further and develops it into a separate discipline altogether. On similar lines, Holacracy seeks to create social technology for purposeful organizations, though not specially targeting software organizations. So, the issue of leadership still continues to be unresolved and rather left to pave its way on its own. Unfortunately, when we want to achieve true end-to-end agility, it is not enough for software teams to be charging at top speeds but leadership not evenly matched to support them well in their endeavors. We clearly have a problem at hand...

    In this talk, we will study how the role of leadership has evolved and what does it look like for agile organizations at present. Many agile methods take an extreme view that limit leadership to team-level collective ownership of leadership. However, that might not be enough because of various reasons. In any non-trivial organization, whether a software organizations or any modern business employing software for business advantage, the reality is that organization units beyond a plain-vanilla software teams do exist. So, how does one go about grooming their top talent for playing an effective part in this process?

    Finally, we will also try to take a shot at some of evolving paradigms. For example, all these management thoughts are still based on the kind of outdated premise that an organization is based on 'boundaries' of operations. However, already we see that model being broken down, and the future teams look more like boundaryless entities bound with nothing but a unifying purpose that brings a bunch of volunteers together for a period of time. If our success increasing depends on such teams being able to effectively self-manage themselves, what role does leadership have to play in it, and are we getting ready for it? 

  • Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    "Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).

    Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.

    Our main question was: As mobile app developers, how should we architect/design our apps for CD?

    We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.

    If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Automate across Platform, OS, Technologies with TaaS

    Anand Bagmar
    Anand Bagmar
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Advanced

    "TaaS" is an open-source product that allows you do achieve the "correct" way of doing integration testing across a variety of products via Test Automation.

    Typically in organizations, there are multiple projects / products. Many organizations like to have a common Test Automation solution across these products in an effort to standardize the framework.

    However, this is not a good idea! Each product should be tested using the tools and technologies that are "right" for it. Yet - these different products talk with each other and you need to test the integration between them in an automated way.

  • Liked Nikhil Joshi
    keyboard_arrow_down

    Build - Measure - Learn : Without spending a fortune

    Nikhil Joshi
    Nikhil Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Michael O'Reilly
    Michael O'Reilly
    schedule 3 years ago
    Sold Out!
    45 mins
    Demonstration
    Intermediate

    Test Requirement Driven Development(TREDD) places a renewed emphasis on quality and accountability, and provides the insight to allow your product development and management teams to make the necessary changes in order to produce outstanding quality products on schedule, in a cost-efficient and highly collaborative manner.

    What separates TREDD from other development methodologies like TDD (test driven development), ATDD (acceptance test drive development), or BDD (behavior driven development), is the status of the test requirement when the product development lifecycle concludes.

    Test Requirement status is the breakthrough element that allows test requirement to provide an objective measurement to the quality of the product development team, so that adjustments can be made for subsequent product development iterations that will ensure quality improves, as well as increase the effectiveness of the product development team.

    Come and learn how your TREDD will catalyze your SCRUM team toward greater capabilities, quality, accountability, and satisfaction!

  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Lean vs. Scrum

    Pavel Dabrytski
    Pavel Dabrytski
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Agile software development has proven to be more successful than traditional methods. However there are many Agile methodologies (Scrum, Kanban, Lean, XP). It is difficult to make a right choice.
    Do you what to know the differences between Scrum and Lean? Perhaps you struggle with your existing Scrum implementation and looking for a better methodology. So did I. I spent many hours looking for continuous improvement beyond Retrospectives and Sprint Reviews. And I found my answer in applying Lean Principles.
    This session will help you to increase your understanding of Lean and Scrum. It will also give you some practical examples of implementing Lean in Scrum teams.

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    schedule 3 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 Neil Killick
    keyboard_arrow_down

    The Guessing Game - Alternatives to Agile Estimation

    Neil Killick
    Neil Killick
    schedule 3 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 Savita Pahuja
    keyboard_arrow_down

    Battlefield Agility

    Savita Pahuja
    Savita Pahuja
    schedule 3 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Battlefield Agility® is a quest to make our deliveries better, more collaborative, faster and effective. It relies on age old principle from the Army to provide a holistic view of the problem landscape which a project team needs to solve and be able to succeed in this, through small collaborative groups working in coordination to achieve the bigger goals.

    Battlefield Agility® derives from the Agile manifesto and principles and adds to it the key ingredient of individual wisdom to create a plan for a team which will help it succeed in successful deliveries . This is a goal based approach to increase MVP and ROI.

    The purpose of this method is to make team members more focused about their work, equal distribution of work in the team and increase productivity.

    Battlefield Agility enumerates the mechanisms of planning, better field view to all team members, ease of multitasking, reduce task switching.

    Key benefits of Battlefield Agility® 

    • A focused approach to software development as development proceeds through small battles to be won
    • Reduced multitasking and better efficiency of team members
    • Faster deliveries as the work is divided to right sized battles to be won
    • Parallel efforts by team members ensure the time to market is significantly lesser
    • Less process overhead as the collaboration is real time and more time is spent on the ground than on meetings
    • Small teams ensure close camaraderie and collaboration among team member
    • The team can even work on disparate work areas ( if required) in order to make best us of their expertise

     

  • Liked Ted Tencza
    keyboard_arrow_down

    Creating a Great Engineering Culture in an Agile workplace.

    Ted Tencza
    Ted Tencza
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Company culture, or its DNA, is one of the most important factors to determing if a company succeeds.  Many companies claim to have great company culture.  But what does this mean, how can you know if your company has a great culture, and how can you go about improving the culture?  This talk will explore what great companies have in common, and share experiences I have had in helping to develop engineering culture during my career.    

    Will also explore how Agile principles help to foster creating the best possible culture for your organization.

  • Liked Prabhakar Karve
    keyboard_arrow_down

    Keep learning even when pressed for time

    Prabhakar Karve
    Prabhakar Karve
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    There are two ways to learn. From books and trainers; and by experiencing life. Life is a great teacher.

    We are always pressed for time; that is a reality. But we can’t do anything till we have enough time; that is a myth. Because we can.

    For learning skills and acquiring knowledge we need time. We can beg borrow or steal. Beg & borrow doesn’t work. Learn interesting ways to steal time.

    Once we take care of time for skills & knowledge, we are ready to handle learning by experiencing. That doesn’t need extra time; if we know how. Through discussions and exercises, master innovative ways like maneuvering attention, watching exceptions and seeking interactions.

    Being at conferences is fine, but we need something while at work where we belong. Use a few simple yet powerful tips to keep learning.

  • Liked Manik Choudhary
    keyboard_arrow_down

    Making of Innovative Solutions: Lean Start-Up and Design Thinking Practices

    Manik Choudhary
    Manik Choudhary
    schedule 3 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Content :

    I will showcase Real Case Study on how Innovative Solutions can be developed using a mix of tools and techniques from Lean Start-Up ,    Design Thinking, User Story Mapping and Lean & Agile Development.

    - Lean Canvas is 1-page document that describes Business Model.

    - Design Thinking is an iterative innovation approach to develop the “Right Product”. Various phases of DT are 1. Understand 2. Observe 3. Define 4. Ideate 5. Prototype 6. Validate.

    - User Story Mapping helps teams get a common understanding of requirements from the user's point-of-view and facilitates creation of clearer backlog items.

    - Lean is right way to reduce waste and to efficiently and rapidly deliver high quality products.

    Summary :

    How the tools and techniques from Lean Start-Up, Design Thinking, User Story Mapping and Lean Development helped us in developing Right Innovative Solution in the right way.

     

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Working at a lean startup

    Vibhu Srinivasan
    Vibhu Srinivasan
    schedule 3 years ago
    Sold Out!
    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 Richard Kasperowski
    keyboard_arrow_down

    Agile for Massive Scale Art and a World Record Attempt

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Imagine quickly organizing 1500 people to work on a massive project together. Imagine creating an art piece that's 100,000 square feet. Imagine doing it in three days and attempting to set a world record.

    Chalkville was a massive scale art piece and world record attempt. This is the story of how we used Agile principles and practices to organize and execute our project over six months. Agile helped us form a team of inspired loving volunteers who would do anything for each other in pursuit of our goal. Does your team have that kind of vision and drive? Find out how we did it and what we learned.

  • Liked Niraj Bhandari
    keyboard_arrow_down

    Adopting Agile - Will you end up missing the soul of your product

    Niraj Bhandari
    Niraj Bhandari
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The aim of this session is to sensitize the audience about the need to have a holistic approach to Agile product development than a blind faith approach.

    Let us take this through an example. Can you name some of the success stories of agile. I did a google search and the list comprised mainly of startups who are anyway doing quick fire work. Try searching for established players and the name which crops up is Salesforce. Facebook is another example which people are quick to point, but facebook doesn’t acknowledge using the Agile as such.

    Let us try and drill down further using these two examples. Salesforce acknowledges that it has tremendously improved the delivery of its features using agile methodologies over time. Great, but wait a point, is the promise of agile to speed execution. No, the premise of agile is to improve the quality of your deliverables and by quality I mean the value derived by a user/consumer. It helps you build the right product. Unfortunately there is no easy way to measure the value delivered by saleforce to its user through these new features.

    Let us now shift gears and look a bit more closely at facebook. Facebook releases features very frequently, almost on daily basis, sometimes even on hourly basis. They are betting big on test automation and continuation integration to ensure that new features don’t cause a breakage. They also seem to be following the agile’s premise of “fail early” by quickly pulling out features which don’t get desired traction from users. So far, it looks a great story and if you are a technical person, you are etching to work for such a company which allows you to experiment with your ideas and put them in production to get instant feedback. Now let us through an alternate perspective – what if some of the features need gestation period before people start liking them. Not every features becomes an instant hit. Remember the classical “Crossing the Chasm” technology adoption lifecycle (couldn't add the image because of editor limitations)

    Some features would need a push to cross the chasm and become successful, but if they are pulled down based on initial traction, you may be losing some of the valuable features. Another twist in tale in this case is what the user research/product management do in this scenario. Aren’t they supposed to do some upfront work to figure out which features have better chances of being accepted and focus energy on helping them cross the chasm. That leads us back to the question we started out with – In our drive to do frequent releases, putting the features out for customers to experience and try, are we missing big picture and just building the product rather than creating a product with a soul. Or is it like we should spend some time upfront to create a “soulful” product and then go full steam in building incremental features. At this point of time it may also  be useful to look at the stories coming out regarding the potential failure of Universal Credit program in UK, which supposedly used Agile but has all but abandoned it. Here are the links, which we would use to structure a discussion around exercising caution while practicing Agile as compared to just rushing into it because everybody else is doing it.

    Resources for structuring discussion around Universal Credit Discussion-

    https://www.techwell.com/2013/07/worlds-biggest-agile-development-project-collapses

    http://www.computerweekly.com/blogs/public-sector/2013/05/dwp-drops-agile-from-flagship.html

  • Liked AOUADI
    keyboard_arrow_down

    Unleash the creativity of your team to innovate

    AOUADI
    AOUADI
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    How the Lean approach can enhance the creativity of your team within software development area ?
    What is at stake for your company and your customers ? How Lean Manufacturing can speed up this creativity process ?
    During this session,
    BG2AA company will present his feedbacks about the implementation of this
    approach for the design of his multi-tenant Software As A Service (SAAS)
     business management platform built on cloud technologies.
    How can the user's experience capture process create the value and innovate
    
Through
     concrete examples, they will explain how visual management, five whys,
    kaizen, A3 report, PDCA ... are powerful quality catalists.

  • Liked Lalatendu Das
    keyboard_arrow_down

    Setting agile teams for success – Use of Operations Research to improve agility

    Lalatendu Das
    Lalatendu Das
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    While there is a good amount of literature on how an existing agile team can self-organize to deliver higher business value, very little has been said about how to use learning from one team on another or how to set new agile teams for long term success.

    In our organization, a typical engagement lasts for 6-8 weeks, leaving very little time for team ramp-up. Setting teams for success was not aspirational but a core ingredient to our service delivery. We explored the field of Operations Research (OR) and applied some of the techniques to software engineering. In this experience report, we are going to share how we leveraged OR concepts such as “Queueing Models” and “Network Optimization” techniques to identify

    - What should be the ideal size of a story to deliver optimal value

    - What should be the optimal team staffing for a given scope of work

    - How to get more predictability on release plans of agile projects

    While our research in this field has been tailored to a very specific type of work we do, the concepts and learning can have wider application.

     

  • Liked Kalyanasis Banerjee
    keyboard_arrow_down

    Large agile transformation applying Kotter's change leadership strategy

    Kalyanasis Banerjee
    Kalyanasis Banerjee
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Link: http://wikireedia.net/wikireedia/index.php?title=Kotters_8_steps_for_implementing_strategy

    Kotter's change leadership framework was established almost 2 decades back. This paper highlights how the same steps helped a structured, waterfall company to start adopting agility to improve time to market. 

    That there is a need for a change was understood when we started. We formed a team that created the sense of urgency.

    We established a common vision ... a simple & easily understandable one.

    We created a framework which can help people understand what does agility means. The framework was created keeping the existing constraints & process (CMMi-5) in mind.

    We worked with an existing team to pilot, proved it works, made a case study and then showcased it to other teams to give an example. This answered the FAQ … does it work for me ? This helped other teams to overcome the fear of uncertainty.

    This created the bottom-up curiosity acres the organisation, in almost every team. They all had a different question now … how can I apply this ? This started the actual transformation.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Exploring the unknown areas of Testing in Analytics

    Anand Bagmar
    Anand Bagmar
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    In the Analytics domain, I will share what I know as different facets of Analytics research and application, and its potential impacts on Testing the same.

  • Liked Neeraj Bachani
    keyboard_arrow_down

    Influence of Japanese Samurai on Agile

    Neeraj Bachani
    Neeraj Bachani
    schedule 3 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    How japanese culture has influenced Agile and list of Japanese terms used in Agile.