TL Diaries | Page 3 | Agile Anti Patterns and Antidotes

Photo by timJ on Unsplash

Estimates provided by Tech Lead or a Single Person

Estimations are team sport. Different roles in a team like UI Designers, Developers, QA and BA participate in this activity. Designer might think of adding a button should be straight forward without having knowledge of the underlying systems. QA adds the points that are not thought by developers like multi device compatibility etc. Every person in different roles brings their perspective to table that other person not able to think.This helps to achieve estimates with high quality compared to the estimates provided by a single person.

Not clearing off the Tech Debt in time

Tech debt can be maintained against cost vs value. This helps in prioritisation of the tech debt. Low cost high value tech debt can be prioritised over high cost low value tasks. Constant refactoring along with stories help in maintaining healthy state of tech debt.

As TL, it’s very important to prioritise and make sure that tech debt is paid off in timely manner.

Photo by Igor Peftiev on Unsplash

Delivery measured in Story Points

Lesson: Never use story points as a measurement of delivery but value delivered by feature.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store