Comments on: Scrum Meetings http://scrummethodology.com/scrum-meetings/ Learn the Scrum Methodology Tue, 13 Mar 2012 16:51:35 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Startup SEO – What SEOs Need to Know | Reputation Expert http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-143475 Startup SEO – What SEOs Need to Know | Reputation Expert Tue, 06 Mar 2012 17:06:07 +0000 http://scrummethodology.com/?p=24#comment-143475 [...] face it. Startups move quickly. Many of them run on the Scrum methodology, which means that they plan one day and then within two weeks changes can be live and big changes [...] [...] face it. Startups move quickly. Many of them run on the Scrum methodology, which means that they plan one day and then within two weeks changes can be live and big changes [...]

]]> By: Startup SEO - What SEOs Need to Know | distilled http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-143446 Startup SEO - What SEOs Need to Know | distilled Tue, 06 Mar 2012 14:45:59 +0000 http://scrummethodology.com/?p=24#comment-143446 [...] (Create News, Do Awesome Things)Let’s face it. Startups move quickly. Many of them run on the Scrum methodology, which means that they plan one day and then within two weeks changes can be live and big changes [...] [...] (Create News, Do Awesome Things)Let’s face it. Startups move quickly. Many of them run on the Scrum methodology, which means that they plan one day and then within two weeks changes can be live and big changes [...]

]]> By: admin http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-118320 admin Tue, 06 Dec 2011 22:20:40 +0000 http://scrummethodology.com/?p=24#comment-118320 We run our teams, and we advise our customers, that the PO is not involved in retrospective meetings, simply because some of the issue raised in the retrospective may have come from that individual. I've heard it argued that since the PO is a member of the team, he should be involved in retrospectives. We run our teams, and we advise our customers, that the PO is not involved in retrospective meetings, simply because some of the issue raised in the retrospective may have come from that individual. I’ve heard it argued that since the PO is a member of the team, he should be involved in retrospectives.

]]> By: Rick Reagan http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-117658 Rick Reagan Sun, 04 Dec 2011 22:56:46 +0000 http://scrummethodology.com/?p=24#comment-117658 At the end, this article says "Since the Product Owner sits this meeting, team members can speak frankly ..." I assume you meant to say "Since the Product Owner sits OUT this meeting..." I believe it depends on the PO relationship with the team. In our case, the PO has been working with most of the team members for 20+ years (unusual, I know) so it seems normal for the PO to be included in the retrospective. At the end, this article says “Since the Product Owner sits this meeting, team members can speak frankly …”

I assume you meant to say “Since the Product Owner sits OUT this meeting…”

I believe it depends on the PO relationship with the team. In our case, the PO has been working with most of the team members for 20+ years (unusual, I know) so it seems normal for the PO to be included in the retrospective.

]]> By: Jim http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-94443 Jim Fri, 26 Aug 2011 09:18:01 +0000 http://scrummethodology.com/?p=24#comment-94443 Hi I have 2 questions? In four weeks time, What happens when the committed task were not finished? Or there are bugs? Ho do we schedule a bug fix after the PO rejected the product? Hi I have 2 questions?

In four weeks time, What happens when the committed task were not finished?
Or there are bugs?

Ho do we schedule a bug fix after the PO rejected the product?

]]> By: SheTech http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-79754 SheTech Tue, 21 Jun 2011 20:58:42 +0000 http://scrummethodology.com/?p=24#comment-79754 In my experience with the retrospective, we had two end-of-scrum conversations: the sprint review included the Product Manager, and the retrospective excluded him/her. That way, we could review the iteration "officially" and help balance resources AND speak frankly about process improvements. In my experience with the retrospective, we had two end-of-scrum conversations: the sprint review included the Product Manager, and the retrospective excluded him/her. That way, we could review the iteration “officially” and help balance resources AND speak frankly about process improvements.

]]> By: Ruud http://scrummethodology.com/scrum-meetings/comment-page-1/#comment-53563 Ruud Fri, 04 Feb 2011 10:26:48 +0000 http://scrummethodology.com/?p=24#comment-53563 Having or not having the PO sit in on the retrospective depends on some factors. How much do you want/need to improve the relationship between the dev-team and the PO? How open is the PO for feedback? How smooth do you want your process to go? I think the PO is important to include in retrospectives; in that way the whole set of processes can be improved. It is however true that when the team gets too technical, the PO might be excused from the meeting. Having or not having the PO sit in on the retrospective depends on some factors. How much do you want/need to improve the relationship between the dev-team and the PO? How open is the PO for feedback? How smooth do you want your process to go?
I think the PO is important to include in retrospectives; in that way the whole set of processes can be improved. It is however true that when the team gets too technical, the PO might be excused from the meeting.

]]>