Can someone please provide inputs on this? Saving Changes...
Pavan Nallamalli, PMPAutomation Manager (SWQA, Tools)| NvidiaPune, Maharashtra, India
Based on my experience in the scrum/agile practice with in several modules, the risk is assessed at each story level along with the story owner + with ranking during the sprint that it's called for. It also depends on the KPI's you have set for the story for example: dependency chain resolve, code complete date, user acceptance test, unit test, etc...
Happy to shed more light if there is a specific use case you're looking for. Thanks. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Each method has its own set of deliverables. SCRUM is not a method, is a framework that you can fill with the deliverables best fits for your initiative. This is something people do not know or forget when use SCRUM or any other method. Because of that you will find lot of implementations and people that said "risk management is not needed in SCRUM" to people that said "we need to create a simple risk register". So, the first thing to do each time you will introduce something is to take into account that it will impact at the whole so an initial analysis about the current state must be done. Returning to the point, I used SCRUM for software and non software projects and I have the opportunity (I am an old man, hehehe) to take training with SCRUM creators and after work with them I decided (and I use) a risk register. That is the deliverable. The other thing you have to create is your risk management process to insert it into SCRUM. In my case, there is no difference about the activities regarding any other risk management process you know (including the process you read into the PMBOK) but the decision is the timming to execute those activities into the SCRUM framework. Saving Changes...
Lonnie PacelliAuthor & President| ProjectManagementAdvisor.comBellevue, Wa, United States
Whatever you do make sure the risk register is clear, easy to understand, accessible by the team, and understandable by management. It doesn't matter whether it's in excel, onenote, sharepoint, or some other tool. just make sure it keeps risks visible and does its job of helping the team identify and mitigate risks. Saving Changes...
