• Liked Ken Furlong
    keyboard_arrow_down

    Upgrade Your Metrics – Cumulative Flow Diagrams and Beyond

    Ken Furlong
    Ken Furlong
    schedule 8 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    When dealing with metrics, most Agile or Lean teams begin with a Burndown Chart.  Unfortunately, that is also where most of them stop.  While a Burndown Chart is a great first step, it only provides a small sliver of the information the team has access to.

     

    In this talk, we’ll be starting at the beginning with what a Cumulative Flow Diagram is, how it relates to a Burndown Chart, its advantages, and where it too ultimately stops.  We’ll then look at additional information radiators that the team can easily use based on existing data to provide transparency to stakeholders and the raw material for continuous improvement.

  • Liked Johanna Rothman
    keyboard_arrow_down

    Becoming an Agile Leader, Regardless of Your Role

    Johanna Rothman
    Johanna Rothman
    schedule 6 months ago
    Sold Out!
    45 mins
    Keynote
    Intermediate

    Agile is about the ability to inspect and adapt to change. Can we become adaptable agile leaders? You don’t need to change your title. You might not need to change where you sit in the organization. You will need to change your mindset to have the courage to lead.

    Johanna will discuss how you can develop an agile mindset, seeing and living the “art of the possible.” We’ll discuss how your mindset influences your change artistry tools, and maybe even what you call yourself. We’ll see how to learn from small successes and continue to make progress, as you change yourself and your organization. You can start your change by changing your mindset to be one of change artistry and leadership.

  • Liked Dave Nicolette
    keyboard_arrow_down

    When you don't need TDD and why

    Dave Nicolette
    Dave Nicolette
    schedule 8 months ago
    Sold Out!
    45 mins
    Others
    Beginner

    Ideas similar to test-infected development or test-driven development have been around quite a while - at least since Alan Perlis wrote about interleaving small amounts of design with small amounts of testing in the 1968 Proceedings of the NATO Software Engineering Conference. Yet, even today, there are endless debates about whether such an approach is useful. Some consider it a baseline practice for any professional developer. Others consider it extra work that adds no value. 

    There's certainly more than one way to achieve a goal. What are the goals, when we write and deliver software professionally? Let's identify the various stakeholders of a software system and enumerate the needs of each. Then, let's walk through several popular ways of building software - TDD and others - and see how we can meet those needs using each approach. 

Sorry, no proposals found under this section.