Project management without meetings.
Meeting driven process is a roadblock to delivering better software.
Uclusion is a new way to communicate and track stories at the same time.
It doesn't matter how you setup your board. A Kanban board is a display only tool - you can't effectively have communication inside of it or get approvals for new stories or reviews of existing work.
It shouldn't surprise you very much that 1950's factory sticky notes don't cover all aspects of modern software development.
This is really making a mockery of Kanban for software development, that's not at all how it's done. I suggest you review this excellent talk from a Microsoft employee on how they've effectively used the Kanban method to tackle issues that we've just discussed. youtube.com/watch?v=CD0y-aU1sXo
Project management without meetings.
Meeting driven process is a roadblock to delivering better software.
Uclusion is a new way to communicate and track stories at the same time.
Frontend developer by day, iOS developer by night. Currently working on learning iOS development and my own blog, Mike Decodes, where I'm decoding the tech industry. Come hang out with me on Twitter!
Project management without meetings.
Meeting driven process is a roadblock to delivering better software.
Uclusion is a new way to communicate and track stories at the same time.
The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprintโs work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It doesn't matter how you setup your board. A Kanban board is a display only tool - you can't effectively have communication inside of it or get approvals for new stories or reviews of existing work.
It shouldn't surprise you very much that 1950's factory sticky notes don't cover all aspects of modern software development.
This is really making a mockery of Kanban for software development, that's not at all how it's done. I suggest you review this excellent talk from a Microsoft employee on how they've effectively used the Kanban method to tackle issues that we've just discussed.
youtube.com/watch?v=CD0y-aU1sXo
Wow the part on estimation in that video is cringey. And naturally it doesn't cover any of the issues we are discussing around the standup like
Work, hopefully ๐
Not according to the Scrum guide: