Friday, October 6, 2017

Do We Need Estimates? #NoEstimates


Topic Title: Do We Need Estimates? #NoEstimates

Initiator: Beth Galambos, PO, Healthesystems

Participants: Ryan Dorrell, Isa Jelez, Marilyn Brislin, Kate Leonardo, Bill Somerville, Sherrie Hanrahan, Patrick McClain, Liliana Talice, Prachi, Gordon Ridge, Riccardo Reimers, Ruchir Shah, Linda Cook, Bashanth Prasannathiotha

Discussion Highlights:
  • High/medium/low confidence on estimates 
    • Seen by business as 'scientific' 
  • Minimal business increment (MBI) 
    • What MUST go out the door to be value to the user 
  • Why even bother with estimating? 
    • Dev teams debating point values 
    • Teams may overestimate if there is a penalty for being 'wrong' in their estimates 
    • They have to learn, especially if coming from a waterfall environment 
  • Fixed vs variable outcome deliveries 
    • Fixed - more time estimating 
    • Variable - less valuable estimating 
  • Larger efforts not focusing on risk and project management, but should 
  • Customer education is important because some think that it's about 'more and faster' 
    • What it's really about is eliminating waste 
  • Who gets involved with estimating? 
    • Whole team, part of team? 
    • High level - representatives of the team 
    • Detailed - the whole team 
  • Retrospecting on stories' estimates 
    • How did we do on that estimate now that the work is done? 
Ideas for Action/Next Steps:
  • Anchor stories - bring a 3 pointer and 5 pointer to refinement/planning and point all stories compared in size to the anchor stories 
  • Kanban - try using a mean or average point value for every story. Do this if you have data to support it.

1 comment:

  1. The effectiveness of IEEE Project Domains depends very much on the situation in which they are applied. In order to further improve IEEE Final Year Project Domains practices we need to explicitly describe and utilise our knowledge about software domains of software engineering Final Year Project Domains for CSE technologies. This paper suggests a modelling formalism for supporting systematic reuse of software engineering technologies during planning of software projects and improvement programmes in Project Centers in Chennai for CSE.

    Software management seeks for decision support to identify technologies like JavaScript that meet best the goals and characteristics of a software project or improvement programme. JavaScript Training in Chennai Accessible experiences and repositories that effectively guide that technology selection are still lacking.

    Aim of technology domain analysis is to describe the class of context situations (e.g., kinds of JavaScript software projects) in which a software engineering technology JavaScript Training in Chennai can be applied successfully

    ReplyDelete