DEV Community

Discussion on: As a lead engineer/manager, what steps can you take for your team to provide better estimations for their tasks?

Collapse
 
jwp profile image
John Peters

Software estimating is impossible. In my 30 years, it never worked until Agile changed the concept of Software delivery.

Agile correctly says Software is never done. Rather, it says we will collect all new requests and order by most value to product owners.

From there it uses Fibonaci numbers to determine difficulty. Anything 8 or above is split into two tickets.

Continual backlog grooming allows for new priorities to be established.

No time commitments are needed because delivery is continuous. Each delivery only contains the most valuable items for a given period. Usually sprints are 2 weeks.

Automated Tests are required for each checkin.

Each checkin requires one or more quality gates. Code reviews ensure the implementation meets the architure, but bans bad coding practices. This ensures, over time, that the code base consists of bullet proof parts to be reused.

Following the suggestions above takes a lot of work and in many cases a retraining of those who love to set dates.

Just say no and never commit to a date, use continuous delivery and include the date setters in the planning meeting.

Collapse
 
dollardhingra profile image
Dollar Dhingra

couldn't agree more