• Shane Hastie
    Shane Hastie
    schedule 1 year ago
    Sold Out!
    90 mins

    A number of agile brands downplay the need for business analysis and requirements management on agile projects, putting large store in the role of the Product Owner.  This paper tackles some of the problems this misconception can result in and shows how effective product ownership almost always requires a team with a variety of skills and backgrounds to be effective.

    Product Ownership requires clarity of vision, alignment with organizational strategy, understanding of the development process and the ability to communicate with a wide variety of stakeholders across all levels both inside and outside the organization.  The complexity of the role is most often more than a single person can (or should) cope with – effective product ownership requires a teamwork approach covering a variety of skills and knowledge.

  • Liked Craig Brown

    Prioritizing backlogs across diverse stakeholders simply and easily

    Craig Brown
    Craig Brown
    schedule 1 year ago
    Sold Out!
    20 mins
    Can we get 100 people to agree on what to prioritise to the top of a backlog? Sure we can. Can we identify a reliable systematic system we can use to get this done in just a few minutes? Of course we can.
    Requires 100 people to meet the claims in the session, but we can run this with ANY amount of people from 3 (Easy!) to 300 (Equally easy!)
    I learned this one from Alistair Cockburn in a pub. It's a neat trick.
Sorry, no proposals found under this section.