What standard "best" practice did you/your team stop doing? What happened?
From CitconWiki
Jump to navigationJump to searchcombined session about 'best' practices / processes that were stopped, and whether it created a new practice
Practices that have been stopped by the participants
- Estimation
- Retrospectives
- Demos
- Strice adherence to coding standards / style
- Testing coverage goals
- Often in place in contracts with supplier relations
- Especially line coverage
- Code reviews for all changes
- non-blocking reviews: rely on pipeline to tackle risks, making review more about architecute, code structure etc. that can be fixed forward (ticketed)
- Detailed technial stories, instead focusing more on user problem
- Too strict avoidance of DRY
- Stories strictly owned by one person
- Leads to WIP >= team members
- Instead focus on getting the important work done as a team
Other thoughts
- Agile manifesto authors in high agency roles, respected experts. Easier to work in certain way compared to the average developer being a small contributor in a large setting
- Croatian saying: "Far from the eyes, far from the heart" (trust and need to meet people)
- People need to eat together to build trust
- Lack of f2f time and eating together likely causing a lot of lack of trust in remote-work times.
- Harder to integrated -> plenty of turnover and shorter stays with a company