Currently we are following a lot of the
Scrum routines like stand ups, refinements, planning 1/2, demo, retro...
The past few months we were heading downwards showing poor performance and delivering bad product/code at the end of the sprint. At first glance it seems as if we are too optimistic when we are planning and committing. After that, during the sprint we hit a lot of problems, and due to the lack of time which partially is caused by the poor commitment we end up with what I've stated at the start of the post - badly implemented features with a lot of bugs. Our PM suggested to try and include some sort of risk management during our refinements/planning which sounds reasonable since it's obvious that there are things that we do not take into consideration during the refinement and when we actually hit a problem it's usually during the sprint when we are already committed.
After some investigation about risk management in Scrum I end up with the idea that maybe Scrum has it's own risk management implemented in it's very nature. The daily stand ups with the questions "What have I done yesterday", "What problems did I hit", "What I'm gonna do today" sounds to me like a pretty good risk investigation and the retro meeting at the end of sprint being a lot longer than an usual stand up meeting is giving a chanse to analyze in more depth things that the team thinks are important.
Since Scrum methodology itself has a lot or rituals that are taking from the time of the team, along with some additions specific for our team like having intentions written for each story, having technical design document (very high level one but still..) we already have somewhat heavy process and I'm wondering is there really some truth in what I think, that retros and stand ups could be a good replacement of standard risk management and could these or other Scrum rituals/routines be used in order to better our risk management rather than including entirely new methodology in our work?