Comments for Scrumphony - Scrum, Kanban and other useful stuff http://blog.scrumphony.com agile, scrum, coaching, lean Wed, 22 Feb 2012 18:35:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on A Checklist for a Distributed Retrospective by Paul Klipp http://blog.scrumphony.com/2011/09/a-checklist-for-a-distributed-retrospective/comment-page-1/#comment-3448 Paul Klipp Wed, 22 Feb 2012 18:35:04 +0000 http://blog.scrumphony.com/?p=480#comment-3448 Hi, Marc! I tried using an online kanban board for retrospectives, since it's really just cards in lists that everyone can create and manipulate, and it worked surprisingly well. Here's a write up on the experience: http://www.lunarlogicpolska.com/blog/2012/02/20/kanbanery-for-retrospectives.html Hi, Marc! I tried using an online kanban board for retrospectives, since it’s really just cards in lists that everyone can create and manipulate, and it worked surprisingly well.

Here’s a write up on the experience:

http://www.lunarlogicpolska.com/blog/2012/02/20/kanbanery-for-retrospectives.html

]]> Comment on Ready For Sprint? by Antoine Alberti http://blog.scrumphony.com/2012/01/ready-for-sprint/comment-page-1/#comment-3338 Antoine Alberti Tue, 24 Jan 2012 18:35:38 +0000 http://blog.scrumphony.com/?p=711#comment-3338 Agree with Vin. If you can split the story into relevant bits, then go ahead. I'll add something I've experienced. The DoR can encourage devs to reject too many stories because they don't meet requirements. That's what materializing borders can lead to. You have to be careful not to replace discussion/negociation with process and rules. Apart from that, I totally agree that having a checklist everyone agrees on definitely helps. Whether it's needed/helpful or not, depends on the relationship between devs/PO/QA. Agree with Vin. If you can split the story into relevant bits, then go ahead. I’ll add something I’ve experienced. The DoR can encourage devs to reject too many stories because they don’t meet requirements. That’s what materializing borders can lead to. You have to be careful not to replace discussion/negociation with process and rules. Apart from that, I totally agree that having a checklist everyone agrees on definitely helps. Whether it’s needed/helpful or not, depends on the relationship between devs/PO/QA.

]]> Comment on Watermelon Reporting by The Quality Of Software Development Cannot Be Measured « Pair Blog about OO-Programming http://blog.scrumphony.com/2011/02/watermelon-reporting/comment-page-1/#comment-3335 The Quality Of Software Development Cannot Be Measured « Pair Blog about OO-Programming Sun, 22 Jan 2012 11:19:58 +0000 http://blog.scrumphony.com/?p=240#comment-3335 [...] serious problems sooner or later, but I’ve seen the opposite. This goes along the lines of watermelon reporting, which you may have experienced, [...] [...] serious problems sooner or later, but I’ve seen the opposite. This goes along the lines of watermelon reporting, which you may have experienced, [...]

]]> Comment on Ready For Sprint? by Vin D'Amico http://blog.scrumphony.com/2012/01/ready-for-sprint/comment-page-1/#comment-3301 Vin D'Amico Mon, 16 Jan 2012 17:00:06 +0000 http://blog.scrumphony.com/?p=711#comment-3301 I need to partially disagree. If a story can be split up into two or more stories and at least one story is meets a DoR, there is no issue. Proceed with the story that is ready! Problems occur when, as you point out, a story is simply not ready and the team decides to "do the best they can". This will inevitably involve some guess work. The wrong guesses will come back to haunt the team and likely result in technical debt. I need to partially disagree. If a story can be split up into two or more stories and at least one story is meets a DoR, there is no issue. Proceed with the story that is ready!

Problems occur when, as you point out, a story is simply not ready and the team decides to “do the best they can”. This will inevitably involve some guess work. The wrong guesses will come back to haunt the team and likely result in technical debt.

]]> Comment on Ready For Sprint? by DerDoubleD http://blog.scrumphony.com/2012/01/ready-for-sprint/comment-page-1/#comment-3300 DerDoubleD Mon, 16 Jan 2012 13:50:58 +0000 http://blog.scrumphony.com/?p=711#comment-3300 Change of mindset and a deeper understanding on what and why has to take place - that needs time and coaching. (DoR was created by the team and given to the PO. He agreed on it...) Change of mindset and a deeper understanding on what and why has to take place – that needs time and coaching. (DoR was created by the team and given to the PO. He agreed on it…)

]]>