2

I work in a team of 8 people and today it receives demands from several stakeholders, some development demands, others operational. When there is development, it is usually done by one person of the team only, and in several situations this model is harmful, for example, when there is exchange in team members.

I've been looking to apply SCRUM, but due to the inability to cease various demands we've received, I'm having difficulty visualizing how SCRUM can be applied. Anyone who has ever had a similar situation could share their experience with SCRUM methodology applied in this context?

6
  • 3
    Scrum is not a silver bullet. If your team is not dedicated to work together on the same project or product, or if they have to work on operational tasks which are not development tasks, then probably Scrum does not apply. – Doc Brown Oct 4 '17 at 21:23
  • Despite the Metaphor, I believe your response is good. Have you ever experienced such a situation? – Uder Moreira Oct 4 '17 at 21:59
  • How far in advance do you receive those demands? Are they day to day? Planned out? It sounds like they are coming in quickly enough you cannot plan them in advance. – enderland Oct 4 '17 at 22:15
  • 3
    I'd strongly advise you to stop wasting your time. My mentor was schooled in Scrum by none other than Ken Schwaber himself who freely admitted that Scrum neither scales horizontally (multi-project), nor vertically (multi-paradigm). Find something else that fits. – Robbie Dee Oct 4 '17 at 22:29
  • @enderland The demands are received day by day. And yes, we could not plan them, because, in theory, we should give flow rate to the demands that IT can not provide. But it turns out they've grown so much that sometimes we have the feeling of automating chaos. – Uder Moreira Oct 5 '17 at 17:16
4

some development demands, others operational

I believe that the Kanban model would be more appropriate for your scenario, because you have tasks that require immediate action, and your scope seems to be defined on-the-fly. Even your development tasks seem to be somewhat like a support ticket, which is assigned to one person that will be working on it until it's done.

The Scrum is not appropriate here because:

  • You have multiple kinds of demands (development but also operational);
  • Your scope is not previously defined (operational demands happen on-the-fly), which make it difficult for you to actually have a backlog, and to plan small deliveries for it;
  • Difficulty to paralellize your demands; Eg: in scrum you have Stories, which need to be planned and be assigned an effort (story points), then you can put your entire team working on sub-tasks within these stories in order to deliver them faster;
  • in scrum you need collaboration from the customer too; for defining all the possible stories (what the customer wants, which compose the product backlog), and for gradually prioritizing them as the project goes;

EDIT: in my opinion, you could try to:

  • Separate the development tasks from the operational;
  • For operational tasks, use the Kanban approach and specify a team allocated for it;
  • For development, you should educate your stakeholders to work and collaborate with you using the Scrum methodology, and also allocate a team for this;
1
  • For OP's benefit, it's still not a good idea to only have one person silos. – RubberDuck Oct 5 '17 at 10:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.