Comments for A Scrum Master's Blog on All Things Agile http://agiletester.wordpress.com Testing Thoughts, Practices and Examples by an Agile Scrum Master and Tester Thu, 27 Aug 2009 22:37:27 +0000 http://wordpress.com/ hourly 1 Comment on Agile 2009 – Experience Report from Yahoo by Agile 2009 – day 3 « devXero's blog http://agiletester.wordpress.com/2009/08/26/agile-2009-experience-report-from-yahoo/#comment-19 Agile 2009 – day 3 « devXero's blog Thu, 27 Aug 2009 22:37:27 +0000 http://agiletester.wordpress.com/2009/08/26/agile-2009-experience-report-from-yahoo/#comment-19 [...] can read Chris’s entire thoughts on the presentation here http://agiletester.wordpress.com/2009/08/26/agile-2009-experience-report-from-yahoo/.  I think he really summed up the points [...] [...] can read Chris’s entire thoughts on the presentation here http://agiletester.wordpress.com/2009/08/26/agile-2009-experience-report-from-yahoo/.  I think he really summed up the points [...]

]]> Comment on Stand-ups by Chris http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-17 Chris Fri, 10 Jul 2009 19:55:42 +0000 http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-17 I think the layout was the "written down" approach to it, to give us an idea on how we should structure it. We still actually go person to person, but what we like to do for each person is identify stories that are done(worked on yesterday and completed), still in progress, or about to start, and then identify what we need then if it is a new story or inprogress to meet our goals. I think this may of been more clear, if i did a sort of logic path diagram, and showed how we started with each person and depending on their responses, we would then go into further inquiry. However we try to make sure everyone speaks and all stories that are approved/inprogress/in build are accounted for(if not yet covered). I think the layout was the “written down” approach to it, to give us an idea on how we should structure it. We still actually go person to person, but what we like to do for each person is identify stories that are done(worked on yesterday and completed), still in progress, or about to start, and then identify what we need then if it is a new story or inprogress to meet our goals.

I think this may of been more clear, if i did a sort of logic path diagram, and showed how we started with each person and depending on their responses, we would then go into further inquiry. However we try to make sure everyone speaks and all stories that are approved/inprogress/in build are accounted for(if not yet covered).

]]> Comment on Stand-ups by Lisa Crispin http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-16 Lisa Crispin Fri, 10 Jul 2009 19:49:27 +0000 http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-16 I like how you cover all these different areas in a shot time. Do you go around the room so each team member speaks, or do you just raise each topic and only people with something relevant speak up? I like how you cover all these different areas in a shot time. Do you go around the room so each team member speaks, or do you just raise each topic and only people with something relevant speak up?

]]> Comment on Stand-ups by Chris http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-15 Chris Mon, 13 Apr 2009 17:17:37 +0000 http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-15 We actually keep this into 15-20 minutes, because as part of our stories we have a pre-story gathering. So the stand up is to identify the pairs that will be undertaking that story and any impediments they have for starting/completeing that story. It moves quickly as we only identify the stories that are inprogress on our Story Board, after that and there is still developer/testers available we then move to the top "approved" story to be worked on and then acknowledge it, and move on. We actually keep this into 15-20 minutes, because as part of our stories we have a pre-story gathering. So the stand up is to identify the pairs that will be undertaking that story and any impediments they have for starting/completeing that story. It moves quickly as we only identify the stories that are inprogress on our Story Board, after that and there is still developer/testers available we then move to the top “approved” story to be worked on and then acknowledge it, and move on.

]]> Comment on Stand-ups by Kevin E. Schlabach http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-14 Kevin E. Schlabach Wed, 08 Apr 2009 17:02:04 +0000 http://agiletester.wordpress.com/2009/04/08/stand-ups/#comment-14 Does this meeting fit into 15 minutes? I support adjusting the scrum/standup agenda once a team is maturing, but this list seems like it is turning into a long meeting. I would be concerned that people find it too long and start to check out. If you can get this format to fit in 15-20 minutes, I like it. I especially like that the PO goes last. They have a voice, but they are secondary to the team! If you are interested in my team's tweaks, check it out here: http://agile-commentary.blogspot.com/2009/02/infusing-some-kanban-follow-up.html Does this meeting fit into 15 minutes?

I support adjusting the scrum/standup agenda once a team is maturing, but this list seems like it is turning into a long meeting. I would be concerned that people find it too long and start to check out.

If you can get this format to fit in 15-20 minutes, I like it. I especially like that the PO goes last. They have a voice, but they are secondary to the team!

If you are interested in my team’s tweaks, check it out here:
http://agile-commentary.blogspot.com/2009/02/infusing-some-kanban-follow-up.html

]]> Comment on Can Testers Make a Difference? A thought inspired by Google’s “Testing on the Toilet”. by David http://agiletester.wordpress.com/2008/05/13/can-testers-make-a-difference-a-thought-inspired-by-googles-testing-on-the-toilet/#comment-13 David Tue, 24 Mar 2009 10:06:16 +0000 http://agiletester.wordpress.com/?p=15#comment-13 Hi Chris, If you are running an Agile project, I think the testers *have* to make a difference. If they do not, then the project isn't being Agile. The methodology relies on the ongoing testing of the sprinted components. The testers should be the 'vital few!' Regards, David jacksguides.com Hi Chris,

If you are running an Agile project, I think the testers *have* to make a difference. If they do not, then the project isn’t being Agile. The methodology relies on the ongoing testing of the sprinted components. The testers should be the ‘vital few!’

Regards,
David
jacksguides.com

]]> Comment on An Introduction to SWAT 2.0 by Chris http://agiletester.wordpress.com/2008/08/06/an-introduction-to-swat-20/#comment-12 Chris Wed, 11 Mar 2009 00:54:01 +0000 http://agiletester.wordpress.com/2008/08/06/an-introduction-to-swat-20/#comment-12 http://sourceforge.net/projects/swat/ you can download swat from here. http://sourceforge.net/projects/swat/ you can download swat from here.

]]> Comment on An Introduction to SWAT 2.0 by Ryan Morgan http://agiletester.wordpress.com/2008/08/06/an-introduction-to-swat-20/#comment-11 Ryan Morgan Tue, 10 Mar 2009 21:48:30 +0000 http://agiletester.wordpress.com/2008/08/06/an-introduction-to-swat-20/#comment-11 Where is the download for this? Where is the download for this?

]]> Comment on Team Dynamics, Don’t be afraid of Change by David http://agiletester.wordpress.com/2008/10/02/team-dynamics-dont-be-afraid-of-change/#comment-8 David Sun, 22 Feb 2009 23:59:59 +0000 http://agiletester.wordpress.com/2008/10/02/team-dynamics-dont-be-afraid-of-change/#comment-8 Hi Chris, Your suggestions for facilitating the team changes make a lot of sense. I think one of the most important aspects for the teams to accept the changes is, as you mentioned, the transferring of knowledge. This removes the 'single point of failure' scenarios that many organisations encounter. This also translates for the team members as having the opportunity to gain new knowledge and skills themselves, which means they don't stay stagnant. Most people will relish an opportunity for up skilling. Regards, David Hi Chris,

Your suggestions for facilitating the team changes make a lot of sense. I think one of the most important aspects for the teams to accept the changes is, as you mentioned, the transferring of knowledge. This removes the ’single point of failure’ scenarios that many organisations encounter.

This also translates for the team members as having the opportunity to gain new knowledge and skills themselves, which means they don’t stay stagnant. Most people will relish an opportunity for up skilling.

Regards,
David

]]> Comment on Retrospective, Scrum Gold Mine or Fool’s Gold? by Mike http://agiletester.wordpress.com/2008/08/27/retrospective-scrum-gold-mine-or-fools-gold/#comment-5 Mike Wed, 27 Aug 2008 16:53:02 +0000 http://agiletester.wordpress.com/2008/08/27/retrospective-scrum-gold-mine-or-fools-gold/#comment-5 I really like the 3rd point, and I feel that its something often missed. By looking at each story and ifentifying impediments you are more likely to see issues that are not more prominent at a global level. I really like the 3rd point, and I feel that its something often missed. By looking at each story and ifentifying impediments you are more likely to see issues that are not more prominent at a global level.

]]>