Development Team – Anti Patterns

Listens to more than one source of requirements (POs and line managers and architects and CEOs and CIOs and …)
Teams not stable
Transparency of what is done in a sprint (invisible work besides sprint backlog)
Drastic and abrupt changes in team sizes kill velocity
Scrum team is not cross-functional – not ITOPS, QA involved
No clear teams – how many teams are there really?
Not enough real alignment between DT and PO
Apathy towards (every) agile tool and methodology in general – even more towards simple todos in jira like moving one task on the board
Estimtes are often not agreed by the whole team. Team uses meritocracy (which is not bad at all)
Teams recognize Titles

Rate this post

Leave a Comment

More from our blog

See all posts

Demo – Anti Patterns

More a presentation than a review No review of timeline or budget…
Continue reading

Planning – Anti Patterns

No looking at previous velocitiy Blind acceptance of P0s proposal Backlog not…
Continue reading

Stand Up – Anti Patterns

Reporting instead of aligning One-by-one in isolation instead of as team basic…
Continue reading