• Liked Ranjith Tharayil
    keyboard_arrow_down

    Ranjith Tharayil - Change Vector Tracking in emergent design

    45 mins
    Talk
    Intermediate

    A reflective design approach to achieve software design agility by modelling change as a vector and tracking it to aid refactoring decisions.

     

    Preface about the talk

    Software design is a field that has always fascinated me and I have tried to be an obedient student trying to learn this art. Like any other design problem, software design is also a wicked problem. Horst Rittel and Melvin Webber defined a “wicked” problem as one that could be clearly defined only by solving it, or by solving part of it .This paradox implies, essentially, that you have to “solve” the problem once in order to clearly define it and then solve it again to create a solution that works.

    Hence you need an architect with magical powers to get your design correct in the first go .This is the core philosophy behind emergent design in which we do not think too much about future . As Uncle Bob sarcastically points out, your customers somehow knows your design and they will come up with a requirement that will break your assumptions and thus your design. In emergent design you embrace aggressive refactoring religiously and few teams rebelliously for the good. It has also been observed that during emergent design refactoring step more focus is towards class design than higher abstract architecture elements. This creates technical debt which can go unnoticed for a long time.

    In this talk I will be introducing a novel technique called change vector tracking that will address the above described problem. Change Vector Tracking is a reflective design approach to achieve software design agility by modelling change as a vector and tracking it through ceremonies like Change Vector Tracking meetings.

    Change vector tracking doesn’t prevent customers from coming up with requirements that would invalidate previous design assumptions, it helps us in monitoring these changes and aids in making informed decisions of where and when to redesign. It helps us keep a check on design debt which otherwise would be overseen and not addressed at the right time .Design debt is invisible to tools initially, only when it grows beyond a scale tools can catch it. Change vector tracking is a technique to capture this design debt in a very early stage. “A stitch in time saves nine”.

  • Liked Maurizio Mancini
    keyboard_arrow_down

    Maurizio Mancini - Scaling Quality by Building it in

    45 mins
    Talk
    Intermediate

    According to the 11th annual State of Agile report by VersionOne, one of the top five reasons for adopting Agile is to “enhance software quality”. In spite of this aspiration, a common pattern in Agile rollouts is the failure to set quality goal improvements from the outset. It is often assumed that if you implement Agile/Scrum then quality will just take care of itself. As many organizations quickly discover, you cannot just “deploy Agile” and expect it to be the silver bullet for a software organizations’ quality issues. Why is this happening so frequently? Is it due to methodical deficiencies, unrealistic expectations, fundamental misunderstanding of Agile, lack of executive support, too much existing technical debt or all of the above?

    If you are questioning whether your Agile rollout is really helping you deliver higher quality software, faster, then this talk is a must to attend. I will discuss the approach I have successfully used in a number of organizations which involves; identifying the necessary building blocks to establish a quality mindset in an organization, moving the organization to a test first mindset, helping the Product Management organization become more Agile, and finally setting the right level of test automation so that you can deliver quality software faster.

    If you are serious about doing Agility at scale, you cannot realistically achieve that goal without ensuring that each team individually delivers quality, and in-turn whole projects/programs that incorporate outputs from the individual teams are delivering quality software. To successfully scale quality, you will need to follow the ‘blueprint’ provided in this presentation.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Design Thinking for Organizational Change

    45 mins
    Talk
    Advanced

    We all know how people use design thinking to create better products and deliver delightful experiences to our users. However, design thinking can be an excellent tool to use for organizational change. In the case of organizational change, our product is the change that we are trying to drive, and our customers are those people who are impacted (internally and externally) and have to live with that change. In the same way that design thinking puts the user front-and-centre for products, it can be used to put people in the organization front-and-centre. In this talk we will discuss how design thinking works and, as a case study, how we have applied it at Scotiabank to help drive adoption of the Bank’s NPS customer insights into building solutions that serve our customers. In that program, previous internal processes were ineffective in pushing relevant data to delivery teams at the right time. Using a Lean or Agile approach would have provided some benefit, but taking a design thinking approach uncovered an array of useful insights to make the whole process more purposeful. Learn from this example to explore how you might incorporate design thinking to drive greater effectiveness and relevance for your team’s body of work.

  • Liked Howard Deiner
    keyboard_arrow_down

    Howard Deiner - How We Get Agile Transformations Wrong By Trying to Do It All So Right

    60 mins
    Talk
    Intermediate

    Sorry to say it guys, but Agile has gone limp over the last few years.  As we get more and more coaches into the mix, both external as well as internal, organizations somehow have forgotten that it’s software that we’re trying to produce.  Not great stand-ups.

    Technical practices matter.  In fact, if we could dispense with ALL process and still create the valuable quality software that is needed, we should do that.  From a Lean perspective, process adds no customer facing value.  But getting rid of all process is crazy talk.  Even Fred George, who promoted “Programmer Anarchy” several years ago never got away from all process.  In reality, his movement was premised on driving business decision making directly into technical decision making, and completely empowering teams to “be” the company.  He premised the concept of “Programmer Anarchy” on using the best and brightest developers out there, and trusting that if they could do something as difficult as create great code that they could do the business decision making as well.

    But perhaps we don’t have the absolute best talent out there.  Perhaps it’s hard to lure people away from Google and Facebook because of the money and the chance to get great work environment and unbelievable work challenges (change the world, anyone?)  Does that mean that we have to go back into the Fredrick Winslow Taylor world view of “The One Best Way”?  With that way becoming making a choice between Scrum, SAFe, Lean/Kanban, and other development processes?

    I’d like to convince you that what’s going to work for your organization and your employees is something in the middle.  I, of course, lean into the “better technical practices will yield better outcomes” frame of mind.  You may as well.  But when Garrison Keillor said, on “A Prairie Home Companion” (a long running radio show on National Public Radio in the States), “Well, that's the news from Lake Wobegon, where all the women are strong, all the men are good looking, and all the children are above average”, that was satire!  And the same is true of your organization.  It can logically be true that all organizations’ developers are all above average.  But we can hold people to an acceptable level of technical practices that will yield in writing better code than merely having a process that talks about writing better code. 

    This session will speak to the specifics of the whats and whys.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Coaching Leadership in an Agile Transformation

    45 mins
    Talk
    Executive

    How do you coach leaders in an agile transformation? How does coaching this group differ from coaching on an agile team? How do you coach Leadership as their peer? Agile is always thought of as being ‘down in the delivery layer’ of organizations. But, for us to be truly successful in embracing agility, we need to be more inclusive of all decision makers in the organization. That starts at the top. There are lot of cultural elements and tools that need to be changed across the organization. This requires dedicated change agents to be positioned within the environment of senior leaders to help them embrace agility in their everyday and strategic decision making. Most people want to do the right thing – it’s all about coaching so that, in the moments where our intentions and our decisions are tested by the status quo, we can help our leaders evaluate their choices. This means being a constant influencer, mirror and educator. And, it means sometimes you have to let things go. Successfully coaching leaders through agile transformation requires very purposeful influencing. In this session, we will discuss how to help bring senior leaders along an agile change journey as well as the primary challenges you are likely to encounter along the way and proven mechanisms to help you push through.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Design thinking and Agile: Infinitely more powerful together

    45 mins
    Talk
    Intermediate

    When Agile first came on the scene it was premised around putting the customer first. But, over the years its focus has evolved and the general perception of Agile today is that it’s mostly a tool for delivering software. Agile’s original focus was mainly on developers and testers, but it never really contemplated design thinking as a discipline. Design thinking, which has been around for decades but is only recently having its ‘moment in the sun’, compliments agile beautifully in that it focuses on trying to solve the right problems for the right people. Design thinking allows us to iterate and test assumptions before too much coding and production-readiness is done, which helps ensure the team is investing in the right things at every stage. It really provides a focus on innovating rather than simply burning down a backlog. In this talk we will discuss different ways to incorporate design thinking into the agile process. You will learn how to yield benefits from bringing these two practices together – most importantly how to best serve the users of the product or service you are delivering. At Scotiabank, we’ve been using these fantastic tools in combination for over a year. It is a journey, and although we haven’t completely solved everything yet, there are a lot of lessons we have learned that can be applied elsewhere.

  • Liked Ardita Karaj
    keyboard_arrow_down

    Ardita Karaj - What's my MVP?

    60 mins
    Talk
    Intermediate

    Are you having trouble finding a small Minimum Viable Product? You've heard about delivering in small, incremental releases, you've tried to chisel out a small slice out of the big product you have to deliver, but what you get is not viable and there's no incremental thinking around releases. Why is this so?

    Join Ardi and Cheezy for this session where they will give you some tips and tricks on how to create your first MVP and then look down the road for future ones. They will give some examples from their experiences and challenges when dealing with teams that believe MVP does not apply to them.

    You will leave this session with some ideas on how to prepare the strategy for your MVPs, how to work with your team to find your small product that is viable and still delivers value, and understand how to organize your efforts to deliver the product incrementally.

  • Liked Ardita Karaj
    keyboard_arrow_down

    Ardita Karaj - Getting Freddie Mercury and Spice Girls together on stage

    30 mins
    Talk
    Intermediate

    Ever been in a situation when the Product Manager comes and asks for “a couple of small changes that are high priority” and the team says “They’re kind of big. Which one do you want first? Really, really!”.  “I want them all! As soon as possible.”.

    There are many directions one can go from here. One can work harder or work smarter. While you probably know ways to work harder, but let’s explore ways to work smarter.

    In this talk Ardita will share techniques that she has used which produce good results. She will talk about Product management, technical backbone, collaboration and how all to get Product managers and teams “singing” together in harmony and with focus.

  • Liked Nayan Hajratwala
    keyboard_arrow_down

    Nayan Hajratwala - Building a Continuous Deployment Pipeline from Scratch

    30 mins
    Demonstration
    Intermediate

    Confused about Continuous Integration vs Delivery vs Deployment? Not sure how to take the next step towards Continuous Deployment?

    In this session, Nayan will remove the confusion around the "Continuous" terms. He'll then show you how to go from Commit to Production with no manual steps, while remaining confident that your production system remains stable. We will do this with a variety of open source tools -- from traditional build & integration tools to modern deployment environments & monitoring. You'll leave the session inspired and ready to build your own Continuous Deployment Pipeline when you get back to work.

  • Liked Jesus Mendez
    keyboard_arrow_down

    Jesus Mendez - Me, My Father's illness and Facilitation. A Happy Ending Story

    75 mins
    Experience Report
    Intermediate

    In this session, I will walk you through some areas of my childhood, introduce you to my father and explain you how I've used facilitation skills to fight back daddy's illness (alcoholism). During this session, you'll learn more about who I am, and if you pay attention or participate, maybe you'll take away two or three facilitation techniques combined with an inspiring and personal happy ending story.

  • Liked Anastasia Valentine
    keyboard_arrow_down

    Anastasia Valentine - Agile Marketing - Is it a 'thing'? How Agile Marketing Kicked Our Team Into High Gear

    45 mins
    Talk
    Beginner

    Is Agile Marketing even a 'thing'? Absolutely! After years of using Agile with Scrum in development capacities, we implemented the approach for all of our marketing efforts. In this session, you will learn how to transition your team to use Agile marketing, how to measure your success and ROI and the benefits of being more responsive and strategic with your marketing resources.

  • Liked Steve Lavigne
    keyboard_arrow_down

    Steve Lavigne - Doing Agile != Being Agile

    Steve Lavigne
    Steve Lavigne
    Product Owner
    OPIN Software Inc.
    schedule 5 days ago
    Sold Out!
    45 mins
    Talk
    Beginner

    There is a very real misconception that people believe because they have a daily stand up once in a while or because they only plan work for the next week at a time that they are being agile.  This simply could not be farther from the truth.

    Doing agile does not mean you are being agile!

    Just because you have a stand-up, does not mean you are being agile.  Just because you only plan work for the next week, does not mean you are being agile.

    There is a lot more needed for a company or a team to be agile and it is a lot harder than you think....but understanding the difference is half the battle.

  • Liked Steve Lavigne
    keyboard_arrow_down

    Steve Lavigne - Going Vertical; A Value Driven Approach to Web Development

    Steve Lavigne
    Steve Lavigne
    Product Owner
    OPIN Software Inc.
    schedule 5 days ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    One of the biggest development hurdles we face when new to any agile framework is switching from a ‘phased’ approach to a ‘vertical slice’ approach.  Individuals and teams often aren’t used to deconstructing projects and problems in this way and we often hear “what about the dependancies” or “the system is too complex”.

    In order to speed up feedback loops and provide instant value to clients, we can take a large feature and break it up into several small pieces that slice through each of the systems architectural layers. We can break down almost any of the features we do within projects into slices that take a couple of days, at most, to get out the door. Each slice is comprised of any work needed to be done in a system architectural layer, as well as, any testing that may need to be done to make it ready for deployment.

     

  • No more proposals exist.