LAST Conference Sydney 2018 Day 1

Thu, Aug 30
Timezone: Australia/Sydney (AEST)
09:00

    Keynote - Mintzberg - 45 mins

09:45

    Morning tea - 15 mins

10:00
10:45
11:30
  • Added to My Schedule
    keyboard_arrow_down
    Nafees Butt

    Nafees Butt - Let the Customer Promise be your Guiding Light

    schedule  11:30 AM - 12:15 PM place room 1 people 5 Interested star_halfRate

    tldr; Organisations exist to fulfil the promise that they made to their customers. This talk describes an approach that uses customer promise, existing culture and the gap between the two as a guiding light for defining goals of an agile transformation.

    Longer version: Leading an Agile transformation is a major undertaking. It is easy to invest all your energies and time at finding the tactical solutions and making strategical changes and not emphasise enough on culture. To ensure that your transformation is more than just a face-lift, it is important to dig deeper into nuances of culture. Attend this talk to walk away with a tool that leaders and change agents can use to understand and evaluate the depth and breadth of their cultural initiative, identify gaps and create action items to address the gaps.
    The tool is based on an upgrade of well-known Schneider's cultural model. It provides an approach for leaders of an organisation to centre their transformation efforts around culture, leadership and customer promise. We will start with the Schneider model to assess the existing culture and the leadership style prevalent in the organisation and will then link it to the customer promise. The model will cover the impact of an evolving customer promise and the complexities of managing it when the enterprise has multiple and often competing sub-cultures.

  • schedule  11:30 AM - 12:15 PM place room 2 star_halfRate

    This talk helps teams of software developers getting more quality work done by improving their code review process.

    Writing software is a collaborative effort. Long are the days of developers hacking alone in their bedrooms. The majority of successful apps and tools are built by a team.

    This communal effort makes the act of reading and reviewing code written by other people as important as writing the code in the first place. Even more so in a workplace that is becoming more and more remote and distributed.

    Yet this is a topic that doesn't get much coverage in blogs and conferences.

    This talks shares techniques to improve the code review process developed over the years and through much experimentation.

    A good code review starts from the code author. Spending time to review the code before submitting it, and adding details in the pull request description goes a long way.

    As reviewers is important to use the right language and to practice empathy. The review should focus on what the code dose, not how the code looks. Discussion about style and patterns should be left for another forum.

    There is a lot that can be automated in code reviews to remove noise and ensure that important things are not missed.

    Time spent improving a team's code review process will pay dividends in better code output and smoother reviews.

  • Added to My Schedule
    keyboard_arrow_down
    Doris Tse

    Doris Tse - Liminal Thinking - Reconstructing our reality Matrix style

    schedule  11:30 AM - 12:15 PM place room 3 people 6 Interested star_halfRate

    "This is your last chance. After this, there is no turning back. You take the blue pill - the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill - you stay in Wonderland and I show you how deep the rabbit hole goes" - Matrix

    Are you prepared to question your own perception of reality?

    If so, join us as we learn how our understanding of reality is shaped by our own beliefs and assumptions and how these can create blind spots.

    How does this relate to Agile transformation? As a Scrum Master, we often face resistance to Agile or learning concepts that would seem blindingly obvious to us. We sometimes walk away from these conversations feeling exasperated and frustrated that other's can find it so difficult to understand and adopt.

    However, often the problem with others failing to see what you see, isn't purely about them. We often forget that as change agents, we bring to the mix a set of our own assumptions and self fulfilling beliefs that also need to be challenged.

    The purpose of this session is to draw on some of the core principles of Liminal Thinking and how they can be applied to Agile transformations.

  • Added to My Schedule
    keyboard_arrow_down
    Peter Lee

    Peter Lee / Henry Soesanto - Using lean tools to create product team balance

    schedule  11:30 AM - 01:00 PM place workshop people 6 Interested star_halfRate

    Product teams often have a huge challenge in balancing the effort towards building for the future and supporting their product today.

    In this workshop you will learn how to use common lean tools like Pareto analysis and PICK matrixes, alongside the cost of delay to ensure that your product teams have a continuing focus of maintaining a health balance between the two.

    At Boral and Campaign Monitor we use this light set of lean tools to help teams maximise the impact they have on the supportability of their systems ensuring they have a healthy balance between building for the future and supporting their product today.

12:15
13:00

    Lunch Break - 45 mins

13:45
14:30
  • Added to My Schedule
    keyboard_arrow_down
    Kelsey van Haaster

    Kelsey van Haaster - P is for password, it’s also for pwned.

    schedule  02:30 - 03:15 PM place room 1 star_halfRate

    “I don’t need a password manager, I use a pattern so I remember them”. Hearing these words strikes fear in the heart of the security professional, and we hear them with terrifying frequency because that is what people (ordinary people, our users) do. They use some kind of predictable pattern, maybe with a little variation on just about every site or application they frequent. Including the corporate ones, we are paid to protect. Let’s face it, who can blame them.

    The most recent set of NIST guidelines for passwords acknowledge the challenges faced by users of our systems and are designed to put the user first by making good security hygiene a user friendly process. At ThoughtWorks we wanted to update our password requirements to meet to meet the new guidelines and we thought, that since we have always had the policy of allowing/encouraging people to buy and to expense a Password Manager, we thought it should be a pretty straightforward process.

    Well, it turns out we were making a lot of assumptions. Our policy was not actually well advertised or consistently applied and anecdotal evidence suggested that we weren't quite as security conscious as we imagined. We set about validating our assumptions with some user research and we learned a lot. On the one hand, we had a lot to be proud of, but there was an awful lot more that could be done.

    As a result of this work, we have set ourselves a goal to drive behaviour change, not only with respect to our corporate information systems but more broadly. Our work is guided by the principle that that good personal security hygiene, amongst ThoughtWorkers, not just at work, but in every aspect of their digital lives is the best way to protect our systems.

    Come to this session to learn about what we found and what we did about it, specifically; how to take your users on a security journey with you, how to leverage the skills of your technologists to support and help your technophobes.

  • Added to My Schedule
    keyboard_arrow_down
    Gabor Devenyi

    Gabor Devenyi / Alex Sloley - The magic number is 10

    schedule  02:30 - 03:15 PM place room 2 people 4 Interested star_halfRate

    Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

    But what is it about the number 10 that makes it the “magic” number?

    Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

    There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

    We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

    Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.

  • Added to My Schedule
    keyboard_arrow_down
    Gus Garcia

    Gus Garcia - The Coding Dojo - Agile Coding For Everyone

    schedule  02:30 - 03:15 PM place room 3 people 1 Interested star_halfRate

    The Coding Dojo is a fun and exciting hands-on activity to learn a new programming language, enhance your knowledge on an already known one, or participate in a session where you can take advantage of the brainpower of the whole group to solve a problem. Beginners and seasoned programmers can participage and share their knowledge or just learn from watching others doing it. Within its many formats, the Dojo can accomodate even large groups of people, where one keyboard is taken in turns by the participans, whilst the others help looking up information with their own devices. The Coding Dojo comprises all values and principles in the Manifesto for Agile Software Development in the way we collaborate and write great code. We are using the Python programming language for this.

15:15

    After noon tea - 15 mins

15:30
15:35
15:40
15:45