Roles and RACI andKanbanPlease see word doc for further instructions.
Week 7 Assignment (2 Parts) PART I – Roles and RACI (10 pts) In the previous Module (Part II Roles) we discussed the importance of roles. Although cross-functional teams are important and roles should be less prescribed from the “team” standpoint (and even less in Kanban) there still needs to be defined roles. A clear delineation on who is in charge (or accountable) for what tasks, activities, and ultimately products/projects is required so there is no confusion and clear accountability. Revisit the Week 4 assignment, this time taking the role as a project manager (in the PO role). Fill out the attached RACI chart on who or what team is responsible, accountable, consulted or informed. Information and Instructions 1. Copy and Paste R,A,C,I from the red box into the appropriate boxes. 2. Not all boxes are required to have a role, but they can, so feel free to give it some thought and fill them out as you go along. 3. Even though R comes before A in “RACI”, Accountable is the highest level of ownership. For example, the PO is ultimately accountable for the product and the ScrumMaster for obstacle removal. 4. There will be ONE Accountable per line and ALL the accountability will be with either the PO, SM, or Dev team. Multiple people/teams can be responsible (or C or I) for an activity but there should really be only 1 accountable role. 5. Sometimes the Accountable and Responsible roles belong to the same person/team, if this is the case just mark it Accountable. 6. Assume “Development Team” includes the team leads that they report to (self-organized). Hints · It is easier to start with accountability first for each line, then responsibility then C and I. · Think about - who is ultimately accountable when something goes wrong or is not completed? Remember accountability is the highest level, it’s who gets blamed if something goes wrong or not completed. · YES! This can vary and there can be certain exceptions depending on the project, there is not a 100% RACI that works on every project. Please use the book, lecture, and slides as a guide for the purposes of this assignment if you are conflicted. · See below for a brief description of all four roles and responsibilities. · Contact me early on if you have any questions, I am here to help. Grading 1. Please fill out and upload the RACI Chart to Canvas, as your Week 7 assignment (Part I). 2. I won’t be going through and grading every cell but there will be certain cells that will be graded as they should have clear cut assignment of one of the four RACIs for that activity. Every line must have “Accountable” assigned to one of the three roles of Agile. · Responsible: People or stakeholders who do the work. They must complete the task or objective or make the decision. Several people can be jointly Responsible. · Accountable: Person or stakeholder who is the "owner" of the work. He or she must sign off or approve when the task, objective or decision is complete. This person must make sure that responsibilities are assigned in the matrix for all related activities. Success requires that there is only one person Accountable, which means that "the buck stops there." · Consulted: People or stakeholders who need to give input before the work can be done and signed-off on. These people are "in the loop" and active participants. · Informed: People or stakeholders who need to be kept "in the picture." They need updates on progress or decisions, but they do not need to be formally consulted, nor do they contribute directly to the task or decision. PART II – Kanban (10 pts) We have spent Weeks 6 and 7 discussing Kanban, how it’s less prescriptive and flexible than Scrum, ways we can combine methods and of course the two main principles of Kanban – 1. Visualizing the data and 2. Limiting WIP. Two additional principles would be that we are continuously trying to improve the process and we are continually working towards smooth flow of work through analysis and metrics. Information and Instructions 1. Construct a Kanban board. 2. Make sure there are at least 3 columns. 3. Indicate a WIP limit on at least 1 column. 4. Have at least 10 activities on the board, these can be boxes or post-it’s with letters or numbers. (Be aware of your WIP limit). 5. In Kanban we are always measuring metrics for process improvement. Which TIME metric are we always looking at and trying to improve? It is updated every time an item reaches “Done” State the answer somewhere on your assignment. Hints · Check out the book or Week 7 Supplemental Material for ideas. · Doesn’t have to be a traditional board but if it is it’s fine, feel free to get creative. Grading 1. Please fill out and upload the document to Canvas, as your Week 7 assignment (Part II). 2. You can use word, excel, PowerPoint etc. for this assignment. You can even draw it out on a board or piece of paper and take a picture. Screenshots are ok too. Please upload the file, document, or picture for this part of the assignment (make sure you answer Question 5). RACI chart Sheet1 FORX RACI Chart KEY: R = Responsible A = Accountable C = Consult I = Inform RACI Chart Name of ActivityProduct ManagerScrumMasterDevelopment TeamStakeholdersLeadership Project CharterAICIIEXAMPLE Communication Plan ----- Risk Management Plan ----- Perform Sprint level activities and tasks----- Coach the team----- Groom the product backlog----- Inspect and Adapt each day (Daily Scrum)----- Collaborate with stakeholders and dev teams----- Plan the Sprint ----- Decision maker for Product on the business side----- Change agent for Scrum----- Participate in planning activities(Portfolio, Prod, Release)----- Address obstacles and problems----- Project Close----- ----- Roles and Responsibilities R = ResponsiblePerson or persons who will do the work or task A = AccountablePerson or persons who is ultimately responsible for the task being done in a correct and timely manner for the client C = ConsultPerson or persons who should/can be consulted before executing the task (can be an SME or alternate resource for that task) I = InformPerson or persons who should be informed of the task Roles / Teams Product ManagerR