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

    Effective 9 Practices to minimize technical debt

    Vinay Krishna
    Vinay Krishna
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt.
    While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many agile practitioners have suggested some practices to avoid or eliminate Technical Debt.
    In this session I shall discuss about a method to get relief from Technical Debt and talks about nine proven practices that a developer can follow to minimize Technical Debt. These practices help to:

    • Change the coder's mindset so that they should use technical practices i.e. various refactoring techniques to reduce technical debt in code and design
    • Developers to plan and manage the time to pay down the debt i.e. determine your living budget
    • Take minimal technical credit in design and code

    These practices have been used and found to be effective when implemented in projects which will be used as a case study.

  • 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