Sorry, no proposals found under this section.
 
Sorry, no proposals found under this section.
 
  • Liked Hameet
    keyboard_arrow_down

    Different Ways to Product Backlog Grooming

    Hameet
    Hameet
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

     

    Product backlog contains list of desired functionalities of an envisioned end product. It provides the bigger picture than the sprint/iteration backlog. If product backlog is neglected and treated as a dumping ground, it can distort the bigger picture and impact the iteration/sprint planning. In essence, a well-groomed product backlog is a prerequisite for a successful sprint planning meeting. As part of product backlog grooming exercise:

    - New items are discovered and described.

    - Existing items are changed or removed as appropriate.

    - Items are prioritized. The most important items being at the top.

    - High-priority items are decomposed and refined for upcoming sprint planning meeting. 

     

    But this poses few questions:

    - How much time should be spent in product backlog grooming?

    - How frequently product backlog grooming should happen?

    - What are different ways to product backlog grooming?

    - How product backlog grooming exercise can be made efficient over time?

     

    In this session, we will touch base on 

    - the factors resulting in growing product backlog

    - the indicators of unhealthy product backlog

    - the impact of unhealthy product backlog on the product development

    - the various approaches to take control of the product backlog 

    - the tips for maintaing a healthy product backlog

     

  • Liked Anand Ananthpadmanaban
    keyboard_arrow_down

    Agile Economics and Project Delivery

    Anand Ananthpadmanaban
    Anand Ananthpadmanaban
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The world is expecting faster roll out of software delivery and expecting better outcomes.Agile has been getting adopted as an answer to address the expectations. The economic conditions influence any development, increasing pressure to balance CAPEX and OPEX expenditures.So the question that comes is whether software development can be governed by engineering discipline alone or we need to move to economic driven system. Establish a more real time governance, project delivery and agile economics.

    This paper shares the experience and point of view on moving to continuous software delivery from software development. It also talks about conventional governance versus economics driven at various levels i.e. organization – business –IT –customer/stakeholders.