The last part of my agile mistakes series is the 3rd - SCRUM PRINCIPLES & RULES issues.
Join the community. Share your wisdom - lessons or link or a question .
I am going to continue with the SCRUM Environment related mistakes/issues.
It is well known that the agile framework should reflect real time customer requirements and develop a viable piece of product at the end of the Sprint. I was engaged with the agile topics and solved the impediments as SCRUM Master and Couch.
The point of the SCRUM Sprint Retrospective meeting is to look at both positive and negative aspects of the project. If the meeting is facilitated by the SCRUM master in a way that the team members only discuss “what is not working”, and the meeting is focused on negative issues, it might damage the work atmosphere and have a negative impact on the team.
In order to manage internal and external projects, many companies are nowadays trying to use agile frameworks. However, in many cases, reading books on agile and being familiar with the agile framework (e.g. SCRUM) is not enough. Companies need to firstly revise their internal processes, reflect on project methodology, define roles and responsibilities descriptions. Before implementing agile management to their projects, they need to set and make sure everybody understands company reporting arrangement.