3 ms·
KANBAN is good at ensuring you do not have too many themes on your plate at the same time. Producing effort estimates is one of the many approaches to start ta
by polotics 4y ago
KANBAN is good at ensuring you do not have too many themes on your plate at the same time.
Producing effort estimates is one of the many approaches to start talking about a task, and not doing it may mean that somebody else's better idea on how to tackle it gets ignored.
Having sprints is a good way to coax people in fully finishing things, it is often needed as many developers tend to jump to the next shiny.
If any of these three things gets used by a bad manager to get fake importance, to put pressure, push people down instead of pulling them up... then get rid of that manager.
- ozim 4y agoFrom my experience sprints ensure that stuff is "good enough" and pushed out the door. Like QA having idea that some icon is not aligned - but yeah it is end of the sprint close it and fix in next iteration and get to work on other thing that has priority now - not aligning some unimportant details. So sprints are also good way to coax people into cutting scope instead of working till it is "perfect". Then pushing back on management to have breathing space and accepting changes only after sprint ends and not when they have a brilliant idea. Sprints and ceremonies create touch points for business people to interact with dev team instead of constantly breathing on their neck or coming up with ideas. Business using JIRA and writing stories/tickets should make sure there is enough context in these so your tickets are living documentation "who,why,where".
- 29athrowaway 4y agoDon't capitalize words that are not acronyms. It's just a 5 letter word, it's not that difficult.
- quesera 4y ago> It's just a 5 letter word, it's not that difficult. Beware the careless pedant!
- polotics 4y agoカンバン then!
- 29athrowaway 4y agoInstant karma. Thank you, phone keyboard. I rate my comment a perfect 7/5.