• Anton Zotin
    Anton Zotin
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    This workshop will help participants to understand how the Kanban method really works.

    We will learn how to use the Kanban method to visualize your current process ("start where you are"). Will figure out how to limit work in progress (WiP); define and make process policies explicit; measure and manage flow.

    Also we will figure out what does it mean to search for opportunities for continuous improvement. We will learn how to increase your team speed and at the same time decrease pressure at work.

    All of these we will touch through extremely hands-on step-by-step simulation using LEGO bricks.

     

  • Liked Sophie Freiermuth
    keyboard_arrow_down

    Integrating UX into the Agile Development Cycle - A case study over 3 projects

    Sophie Freiermuth
    Sophie Freiermuth
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Beginner

    User Experience design is a product design discipline which sits throughout a product's lifecycle, from inception to development to maintenance and all the way to retirement. Waterfall enabled the discipline to have ample time and produce extensive design, in a "big design upfront" approach which rarely involved technical capabilities, and resulted in difficulties in build. The adoption of agile by product development team has offered UX a unique opportunity to work in a much more joined-up manner, and expend the design into the development, enabling the entire team to react to change.

    As a UX designer, I have over the last 7 years developped a solid appreciation of working embedded in an agile development team, and would like to share my experiences through 3 specific projects, sharing my learnings to help development team on-board the UX practitioner, their tools, practices and skills.

    This session will be a case study over 3 projects, highlighting the learnings and steps of the integration of UX into the development cycle. I'm taking Alistair Cockburn's sequence of SHU-HA-RI to detail the progress of my practice and will pay great attention to sharing sufficient context that my experiences and outcomes can be translated to your own projects and team setups.

  • Liked Mikael Lundquist
    keyboard_arrow_down

    10 times better quality with agile transformation. How we did it!!!

    Mikael Lundquist
    Mikael Lundquist
    Fredrik Hedlund
    Fredrik Hedlund
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Abstract

    In 2011 the Ladok section at ITS had serious quality issues, resulting in dissatisfied customers. At the beginning of 2012 the section started an agile transformation, in steps, throughout the whole section. One year later the whole section had transformed and currently the section now eats, sleeps and breathes Agile. The quality has improved remarkably and our customers are understandably much more satisfied. Besides satisfied customers, our employees are happier.

    The ideas to try agile came from the people working in the project and we think that was an important factor for the success.

    We are going to talk about our experiences of this transformation and how the transformation contributed to the remarkable increase of the quality. The talk will cover the background, our roadmap, the result of the transformation and the factors of success.

    We have identified two key factors of our success that we will promote a little extra during our talk.

     

    Presentation technique

    We are going to perform this presentation in an agile way, in the way we interpret scrum. This means that we are going to interact with the audience and we expect them to influence our presentation.

    The point is to not just talk of how we did, but also show it on stage. We also think that this is a good way for the audience to really get the most out of the presentation.

     

    We want you to prioritize the presentation parts

    We consider the different parts of the presentation as the presentation backlog. We want the audience to prioritize the parts of our presentation, in advance. Prioritize here.

     

  • Liked Yuval Yeret
    keyboard_arrow_down

    Kanban - A Way Towards DevOps in the Legacy Enterprise

    Yuval Yeret
    Yuval Yeret
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    DevOps is a higher form of agility. It is a blueprint for a great culture and and process between the different groups involved in the delivery pipeline. The big question is how to achieve it. If you are founding a startup today, it can be quite easy to take that blueprint and use it to create your process, hire the right versatile flexible people, and start delivering without any technical/automation debt or friction. But most of us are not founding new startups. Most of us already have a running operation with people, culture, process that matured over the years and despite its flaws is currently the way we do things. Changing that is non-trivial. For things to change people need to understand WHY change, what we are changing, and we need an effective process for managing the change itself (HOW to change). So what ARE we changing to? DevOps is highly focused on looking at the whole value stream from idea to value and ensuring effective flow through this pipeline. Kanban is ONE way of HOW to change. It starts by visualizing all the work flowing in the pipeline, then managing the flow focusing on finishing things end to end rather than starting in order to stay busy. It continues to what we call the “Work in process Diet” – Straining the flow more and more in order to identify obstacles to tighter and tighter DevOps culture/operation and faster feedback cycles. You can expect to come out of this session with ideas how to take your current operation and DevOpsify it in a safe evolutionary way using the Kanban method.

  • Liked Karthik Kamal Balasubramaniam
    keyboard_arrow_down

    It's not an Agile story

    Karthik Kamal Balasubramaniam
    Karthik Kamal Balasubramaniam
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Having worked with multiple Agile teams, I realize that most problems the teams have to deal with are often related to issues that are beyond the scope of any Agile framework. These issues are often related to people and the surrounding eco-system. The success of any Agile implementation is largely dependent on this H(uman)-factor which is intrinsic to any team/organization. This H-factor has always been a pandora's box, that we would like to avoid owing to  the amount of complexity and the uncertainty involved.

    Here is my humble effort to try and identify few common traits that I have observed with people across Agile teams and organizations. The idea here is not to stereotype people, but to present an approach/strategy to accommodate different kinds of people in an Agile eco-system.

    In this talk, I would like to present 5 characters in a fictional story and the various strategies I have adopted to coach them.

    After all one size doesn't fit all!

  • Liked Gautam Rege
    keyboard_arrow_down

    Don't test your code!

    Gautam Rege
    Gautam Rege
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    Testing is overated. Let's correct that statement - "Manual Testing is overrated". In this this talk, I plan to take you on whirlwind tour of why an Agile outfit does not need manual testing at all and how to get fantastic Quality Assurance without manual testing.

    In this talk - I outline a agile process with a difference - everyone is a developer and a tester. However, there is no dedicated QA people. In fact, this process does not require anyone other than the developers and one process/product owner.

    Development using a central repository like Github that is integrated with a Continuous Integration service (like Travis, CircleCI or Semaphore) and further integrated with a Code Quality checker like Code Climate or Pull Review is part of the automation trick. Then comes the development processes like pull request between branches (enabling peer code review) and Automated Deployment to a staging server.

    Finally, the pixel perfection or meeting product specificaiton via Project Management tools (which are integrated with the Code repository) gives the product owner (or the client) complete confidence in not just the functionality but also the quality of the code. 

    This approach can be applied to evolving products too and I discuss how to work in short sprints that always keep changing and guarantee that "The product owner gets the money's worth and the development team gets their works worth!".

     

  • Todd Little
    Todd Little
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    In this highly engaging workshop attendees will experience estimating, planning and delivering a new product and product features.  The uncertainty in value and costs will be resolved through rolling dice based on the stories that the team selects and prioritizes.   The teams will run through 3 iterations of story cost, value estimation, and product feature delivery.  Points will be scored for delivering product features and meeting release and iteration commitments. 

    Dealing with uncertainty is one of the largest challenges that teams face.  The simulation aims to have levels of uncertainty in value and delivery that are commensurate with those found in software development.  Some of the key tools for dealing with uncertainty are integrated into the simulation.  In particular, the simulation covers these 4 areas:

    • Value of Information
    • Value of Flexibility
    • Cost of Delay
    • Value of Uncertainty

    Attendees will come away with a better understanding of the challenges of working with uncertainty in software projects, and will learn some of the tools that are at their disposal for managing this uncertainty.

  • Liked Evan Leybourn
    keyboard_arrow_down

    Starting with Kanban: A practical workshop on Value Stream Mapping and WIP

    Evan Leybourn
    Evan Leybourn
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    So you’ve heard about this Kanban thing and want to know where to start, or maybe you’ve been using it for a while and you want to know where to go. In this hands-on workshop, we'll start at the very beginning and teach you how to build a Value Stream Map and use that to define your inital Kanban and WIP limits.

    If these terms don’t make sense to you, then you need to come along for a fun interactive workshop.

  • Liked Niranjan N V
    keyboard_arrow_down

    Mr.Agile Leader - “ Develop People or Solutions”

    Niranjan N V
    Niranjan N V
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    Based on my experience of coaching/ training agile teams for 5 years, one of the important reasons for agile teams are impacted, is the personal leadership style of Agile Leaders(Scrum Master, Senior Managers etc) . I have summarized following, factors or impediments for creating effective agile teams

    • The agile teams effectiveness depends on personal leadership style of agile leaders(Scrum Masters, Senior Management etc)
    • Often Agile leaders focus more on “delivering solutions” than “developing people”.
    • Agile leader need not specify work requirements, all that team needs is - empowerment, autonomy to work.
    • The agile team needs more support through mentoring, coaching from agile leaders to exhibit the culture “Being Agile” than “Doing Agile”.
    • Agile leaders need not be an Expert to coach agile teams.
    • Agile teams needs to be taught on Identifying Problem, Problem solving skills and corrective actions and demonstrate steady, small and continuous improvement.

     

    My inspiration to write here, is derived from the book “ Managing Excellence” by David Bradford and Allan Cohen, and reading blogs, articles along with my own experience.

     

    The entire presentation will be done in “Pecha Kucha Style” with less words and more background pictures, in each slide. The most of the message is conveyed through pictures. The presenter will talk maximum 30 secs on each slide. The slides keep changing automatically after 30 secs, so that presenter continues the discussion in the next slide automatically

  • Liked Evan Leybourn
    keyboard_arrow_down

    How much will this cost?

    Evan Leybourn
    Evan Leybourn
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Beginner
    "How much will this cost?" 
    "How long will it take?" 
    "What am I going to get?" 

    These are the questions that every Agile project gets asked at some point. And while "as much as your willing to spend", "as long as necessary" and "whatever you ask for" are perfectly acceptable, many customers are uncomfortable with these answers. This may reflect more on the customer then the team, but can lead to the misconception that the development team is writing themselves a blank cheque. How then does an Agile team define and scope a project where the customer requires fixed time, cost or scope? 

    This presentation will provide guidance and direction on how to quote for and budget Agile projects, as well as how to change the questions in the first place.
  • Liked Tathagat Varma
    keyboard_arrow_down

    Design Thinking

    Tathagat Varma
    Tathagat Varma
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    An intro to design thinking ideas...

  • Liked Todd Little
    keyboard_arrow_down

    Mythbusting Software Estimation

    Todd Little
    Todd Little
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Estimating software projects has proven to be particularly challenging.  Over-running schedules happens frequently in our industry.  As a result software estimation is often viewed as a black art.  In this session Todd will look into some of the reasons for these challenges by exploring a number of myths of software estimation and then setting out to validate or bust these myths.

    Some of the myths that will be explored include:

    • Historical Estimation Accuracy
    • Relative Estimation
    • The Cone of Uncertainty
    • Velocity
    • Scope Creep
    • Estimation Tools
    • Wisdom of Crowds
  • Diana Larsen
    Diana Larsen
    schedule 2 years ago
    Sold Out!
    90 mins
    Workshop
    Beginner

    Over the past ten years, software development teams using Agile approaches to work have adopted retrospective meetings as a critical practice for learning and continuous improvement. To the extent that practitioners say, “If you’re not holding iteration retrospectives, you’re not doing Agile.”

     Agile retrospectives at the end of each iteration or work increment set aside time for the team to examine feedback from current conditions and develop targeted tactics to keep the project on track. Many practitioners experience retrospectives as great means for detecting good, poor, and missing practices; as a handle to make tacit knowledge about effective practices explicit; and to define improvement actions in order to deal with ineffective or inefficient technical, process, and teamwork practices.

    However, too many teams and practitioners don’t reap the benefits that effective retrospective meetings can provide. Too many retrospective meetings receive cursory or inadequate facilitation. Too many retrospective meetings are held to  “check the box” on the project management template, rather than to focus on real improvements. For too many teams, the action plans coming out of retrospectives are never implemented or revisited. Too many teams seek to shift blame and responsibility for action through the retrospective.

    In too many organizations, retrospective meetings don’t deliver the promised return on time invested (ROTI).

    In this session, you’ll learn how to get the most from your retrospective practices. Diana Larsen, co-author of Agile Retrospectives: Making Good Teams Great, will introduce you to a simple framework for getting better outcomes from retrospective meetings, suggest ways to maintain the relevance of improvement to the work of your team, and provide tips and pointers to get great returns from the time your teams devote to every meeting. 

  • Jeff Lopez-Stuit, CEC
    Jeff Lopez-Stuit, CEC
    schedule 2 years ago
    Sold Out!
    20 mins
    Pecha Kucha
    Beginner

    How can teams that have to deal with large, complex legacy systems get through planning and get to work? The title character of the classic American horror film, "The Exorcist" was a master at this..

    Pecha Kucha Talk Summary:

    • Introduction: Creating understanding through conversation can be very difficult for teams dealing with complex, legacy systems.

    • Introducing Regan McNeil: Poor Regan McNeil was starting go insane, but a team of doctors and specialists in close, face-to-face collaboration, couldn't solve her problem.

    • The Exorcist: The Exorcist knew how to have just enough conversation to get to work, so his team could deliver the value everyone had been working and praying for.

    • Summary: "In life, understanding is the booby prize". Sometimes the quest for understanding can be an impediment to delivering value. Having faith in self-organization, sometimes its best just to get to work.
Sorry, no proposals found under this section.