Many organizations try to implement Scrum but unless they adopt Scrum completely they don't achieve the success what they are expecting by implementing Scrum. Many times ScrumButs are the reasons why teams can't take the full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum.
In Scrum every Role, Event or a Timebox is designed to provide the desired benefits and address predictable problems. Sometimes organization implement Scrum but with certain modifications to Scrum Roles, Events or Timeboxes; because of some organizational challenges. In this scenario, organizations are implementing Scrum but with modifications to some of the aspects of Scrum and it is called ScrumBut.
ScrumBut has a syntax (ScrumBut)(Reason)(Workaround)
Examples
- (We are following Scrum but )(sometimes we get ad-hoc requirements,)( so we update the Sprint Backlog in the middle of Sprint and don't achieve the goal of the Sprint)
- (We are following Scrum but)( some team members are at different location, )(so they don't attend the Daily Scrum Meeting)
- (We are following Scrum but)( we think Backlog Grooming Session is a waste of time, )(so we don't do Backlog Grooming Sessions)
- (We are following Scrum but )( team members are very busy in doing assigned tasks, )( so they don't update hours remaining on daily basis)
As mentioned above, each of the Scrum Roles or Events has certain purpose and if you tweak it for your project situation then you won't get full benefits of Scrum. So it is recommended to implement Scrum by avoiding any of the ScrumButs.
No comments:
Post a Comment