Hi,
We fibonacci estimate our tasks, do planning and then we have 2 weeks sprints. It works perfect for us when the tasks we have depend only on us.
The problem is that we also need things done from partners to implement, and these different partners are unpredictable: they could finish a task in a day or in a week or in a month. These are tasks that our partners need to do (so in theory they shouldn't go in the sprint, right?), but some of our team members have to follow up on these tasks: nag, communicate, ask what the status of the tasks are, push them, etc. Also when they finish the task someone of our team has to test it. How can we track this effort that WE make from our partner's tasks?
What we do for now is create tasks like "Follow up PartnerX and test" and estimate accordingly. Those tasks are going to be blocked until our partners do their part, so they can be blocked for many sprints. Is that okay? Does it make sense to track this tasks if they don't really live in our sprint workflow? Should we be having tasks about following up with partners?
BTW: we use Jira and some team members don't want to have different boards for this because it would lose visibility.
Any help is appreciated! Thanks.
On Aug 2, 2017, at 11:33 AM, Amina Layco <amina...@gmail.com> wrote:The problem is that we also need things done from partners to implement, and these different partners are unpredictable: they could finish a task in a day or in a week or in a month. These are tasks that our partners need to do (so in theory they shouldn't go in the sprint, right?), but some of our team members have to follow up on these tasks: nag, communicate, ask what the status of the tasks are, push them, etc. Also when they finish the task someone of our team has to test it. How can we track this effort that WE make from our partner's tasks?
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumalliance+unsubscribe@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
Amina,Isn't great how Scrum has made obvious the difficulty caused by weak connections with partners? Help your leaders see and fix this impediment. Ron has good ideas about making it more obvious.Alan
On Wed, Aug 2, 2017 at 8:33 AM, Amina Layco <amina...@gmail.com> wrote:
Hi,
We fibonacci estimate our tasks, do planning and then we have 2 weeks sprints. It works perfect for us when the tasks we have depend only on us.
The problem is that we also need things done from partners to implement, and these different partners are unpredictable: they could finish a task in a day or in a week or in a month. These are tasks that our partners need to do (so in theory they shouldn't go in the sprint, right?), but some of our team members have to follow up on these tasks: nag, communicate, ask what the status of the tasks are, push them, etc. Also when they finish the task someone of our team has to test it. How can we track this effort that WE make from our partner's tasks?
What we do for now is create tasks like "Follow up PartnerX and test" and estimate accordingly. Those tasks are going to be blocked until our partners do their part, so they can be blocked for many sprints. Is that okay? Does it make sense to track this tasks if they don't really live in our sprint workflow? Should we be having tasks about following up with partners?
BTW: we use Jira and some team members don't want to have different boards for this because it would lose visibility.
Any help is appreciated! Thanks.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
Hi AminaGreat advice from Ron, as usual. In addition, I often offer the following rule to teams I am working with:"Never accept a product backlog item into the sprint where a third party dependency exists unless the third party dependency commits to deliver within the sprint"--Derek
--Derek DavidsonAgile Coach & Professional Scrum TrainerAuthor of the Agile AnnexHelping large organizations successfully adopt the benefits of scrum
On Wed, Aug 2, 2017 at 4:33 PM, Amina Layco <amina...@gmail.com> wrote:
Hi,
We fibonacci estimate our tasks, do planning and then we have 2 weeks sprints. It works perfect for us when the tasks we have depend only on us.
The problem is that we also need things done from partners to implement, and these different partners are unpredictable: they could finish a task in a day or in a week or in a month. These are tasks that our partners need to do (so in theory they shouldn't go in the sprint, right?), but some of our team members have to follow up on these tasks: nag, communicate, ask what the status of the tasks are, push them, etc. Also when they finish the task someone of our team has to test it. How can we track this effort that WE make from our partner's tasks?
What we do for now is create tasks like "Follow up PartnerX and test" and estimate accordingly. Those tasks are going to be blocked until our partners do their part, so they can be blocked for many sprints. Is that okay? Does it make sense to track this tasks if they don't really live in our sprint workflow? Should we be having tasks about following up with partners?
BTW: we use Jira and some team members don't want to have different boards for this because it would lose visibility.
Any help is appreciated! Thanks.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumalliance+unsubscribe@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at https://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
On Aug 2, 2017, at 1:25 PM, Amina Layco <amina...@gmail.com> wrote:Thank you for the reply. About your 1st and 2nd points, there isn't much we can do about, we tried to make this situation better but we just have to accept different partners work in different time schedules and their own priorities change everyday.
We don't have a continuous build but I didn't understand how you mean it could help? We could put in our sprint board the tasks that our partners are doing. But is it the right thing? It will quite ruin the velocity and predictability of our own sprints.
I quite like the Big Visible Chart idea! So in there we can track all this non development effort that we do when we communicate with partners, right?
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumalliance+unsubscribe@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.