YOW! Deep Dive Workshop 278

Thu, Feb 28
08:30
  • Added to My Schedule
    keyboard_arrow_down
    Jeff Patton

    Jeff Patton - Passionate Product Ownership A Certified Scrum Product Ownership Workshop (Sydney)

    schedule  08:30 AM - 04:30 PM place Grand Ball Room 1 shopping_cart Reserve Seat

    Product Ownership is hard! If you’re working as a product owner in an Agile team, you already know this is the toughest and most critical role in a successful product organization.
    If you’re a UX practitioner, senior engineer, or marketing professional in your organization, it may seem like adopting Scrum or Agile development has stripped away your ability to contribute as a product decision maker.

    If you’re adopting an Agile approach, your organization may be struggling with bloated backlogs that aren’t well understood, stressful planning meetings that last too long and fail to get at details needed to deliver predictably, a nagging feeling that you’re building the wrong thing, a lack of time to work with customers and users, chronically late delivery, and frustrated business stakeholders…There’s hope!

    The Passionate Product Ownership workshop takes on the bad assumptions and bad practices that often emerge from overly simplistic approaches to agile development and Scrum. Jeff Patton will leverage his past product leadership experience, and years of coaching product teams to teach an effective product ownership strategy.

YOW! Deep Dive Workshop 279

Fri, Mar 1
08:30
  • Added to My Schedule
    keyboard_arrow_down
    Jeff Patton

    Jeff Patton - Passionate Product Ownership A Certified Scrum Product Ownership Workshop (Sydney)...continued

    schedule  08:30 AM - 04:30 PM place Grand Ball Room 1 shopping_cart Reserve Seat

    Product Ownership is hard! If you’re working as a product owner in an Agile team, you already know this is the toughest and most critical role in a successful product organization.
    If you’re a UX practitioner, senior engineer, or marketing professional in your organization, it may seem like adopting Scrum or Agile development has stripped away your ability to contribute as a product decision maker.

    If you’re adopting an Agile approach, your organization may be struggling with bloated backlogs that aren’t well understood, stressful planning meetings that last too long and fail to get at details needed to deliver predictably, a nagging feeling that you’re building the wrong thing, a lack of time to work with customers and users, chronically late delivery, and frustrated business stakeholders…There’s hope!

    The Passionate Product Ownership workshop takes on the bad assumptions and bad practices that often emerge from overly simplistic approaches to agile development and Scrum. Jeff Patton will leverage his past product leadership experience, and years of coaching product teams to teach an effective product ownership strategy.

YOW! Workshops Day 276

Thu, Oct 3
09:00
  • Added to My Schedule
    keyboard_arrow_down
    Jeff Patton

    Jeff Patton - Passionate Product Ownership A Certified Scrum Product Ownership Workshop (Sydney)

    schedule  09:00 AM - 05:00 PM place Room 1 shopping_cart Reserve Seat

    Product Ownership is hard! If you’re working as a product owner in an Agile team, you already know this is the toughest and most critical role in a successful product organization.
    If you’re a UX practitioner, senior engineer, or marketing professional in your organization, it may seem like adopting Scrum or Agile development has stripped away your ability to contribute as a product decision maker.

    If you’re adopting an Agile approach, your organization may be struggling with bloated backlogs that aren’t well understood, stressful planning meetings that last too long and fail to get at details needed to deliver predictably, a nagging feeling that you’re building the wrong thing, a lack of time to work with customers and users, chronically late delivery, and frustrated business stakeholders…There’s hope!

    The Passionate Product Ownership workshop takes on the bad assumptions and bad practices that often emerge from overly simplistic approaches to agile development and Scrum. Jeff Patton will leverage his past product leadership experience, and years of coaching product teams to teach an effective product ownership strategy.

YOW! Workshops Day 277

Fri, Oct 4
09:00
  • Added to My Schedule
    keyboard_arrow_down
    Jeff Patton

    Jeff Patton - Passionate Product Ownership A Certified Scrum Product Ownership Workshop (Sydney)...continued

    schedule  09:00 AM - 05:00 PM place Room 1 shopping_cart Reserve Seat

    Product Ownership is hard! If you’re working as a product owner in an Agile team, you already know this is the toughest and most critical role in a successful product organization.
    If you’re a UX practitioner, senior engineer, or marketing professional in your organization, it may seem like adopting Scrum or Agile development has stripped away your ability to contribute as a product decision maker.

    If you’re adopting an Agile approach, your organization may be struggling with bloated backlogs that aren’t well understood, stressful planning meetings that last too long and fail to get at details needed to deliver predictably, a nagging feeling that you’re building the wrong thing, a lack of time to work with customers and users, chronically late delivery, and frustrated business stakeholders…There’s hope!

    The Passionate Product Ownership workshop takes on the bad assumptions and bad practices that often emerge from overly simplistic approaches to agile development and Scrum. Jeff Patton will leverage his past product leadership experience, and years of coaching product teams to teach an effective product ownership strategy.

YOW! Workshops Day 592

Fri, Aug 14
09:00
  • Added to My Schedule
    keyboard_arrow_down
    Josh Long

    Josh Long - Cloud Native Java Workshop (Online)

    schedule  09:00 AM - 05:00 PM place Grand Ball Room 1 shopping_cart Reserve Seat

    Join YOW! Online for discounts on conferences and online workshops like this one - as well as great monthly content from our international expert speakers!


    This online workshop will take place over two days, leaving time in between to work on exercises.:

    Friday 14 August   9am - 1pm AEST |

    Tuesday 18 August 9am - 1pm AEST


    “It is not necessary to change. Survival is not mandatory.” -W. Edwards Deming

    Work takes time to flow through an organization and ultimately be deployed to production where it captures value. It’s critical to reduce time-to-production. Software - for many organizations and industries - is a competitive advantage.

    Organizations break their larger software ambitions into smaller, independently deployable, feature -centric batches of work - microservices. In order to reduce the round-trip between stations of work, organizations collapse or consolidate as much of them as possible and automate the rest; developers and operations beget “devops,” cloud-based services and platforms automate operations work and break down the need for ITIL tickets and change management boards.

    But velocity, for velocity’s sake, is dangerous. Microservices invite architectural complexity that few are prepared to address. In this talk, we’ll look at how high performance organizations like Ticketmaster, Alibaba, and Netflix make short work of that complexity with Spring Boot and Spring Cloud.

    In this workshop we'll look at how to build cloud-native applications that are destined for production. A cloud native application is:

    • elastic
    • agile
    • observable
    • robust

    A cloud native application is one that is designed to fully exploit a cloud platform both in the application layer - where things decompose into microservices - and at the data layer where NoSQL offers better horizontal scaling and fitness for specific purposes. This is what we mean by elastic.

    A cloud native application is one that is agile. It should be easy to write, change, test, deploy and operate. If the cost of change is prohibitive then normal people under normal situations won't do it. We must make doing the right thing - that which supports change - the easy thing.

    A cloud native system is observable. It must support at-a-glance insight into what is happening in the system and support remediation. It must be instrumented at the application and systems levels to support the effort of crisis-management.

    A cloud native application is one that is fault tolerant, or robust. If a service should fail, the system must be able to recover and degrade gracefully. Instead of trying to build a system that is predicated on the lie that things are highly available, build instead to optimize for time to remediation.