AGILE DEVELOPMENT FRAMEWORKS: THEORY CMU SE 17604 EDUARDO .

AGILE DEVELOPMENT FRAMEWORKS:THEORYCMU SE 17604EDUARDO MIRANDAASSIGNMENT 1: DEFINING, PLANNINGAND EXECUTING A SCRUM PROJECTVERSION 1.02017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusCONTENTSThe assignment . 3The Time Reporting System . 3Introduction . 3System description . 3Deliverable 1: User stories and story map. 7Deliverable 2: Planning poker estimation. 8Deliverable 3: Sprint planning . 9Class activity: Execute the Sprint . 10Deliverable 4: Retrospective report . 14Appendix A: Sprint Simulation . 15Introduction . 15Definition of Terms . 17Instructor script . 19Student script . 20Simulation rules . 21General . 21Events Definition List . 22Effort Adjustment Rules for task allocation . 26Effort adjustment rules for progress . 27Reporting Rules. 30Closing . 33Events Definition . 34Progress Definition . 35Appendix b. Data for the creation of the prize wheels – Students do not need to worry about this .36Events Wheel . 37Progress Wheel . 37Acknowledgments: . 372017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusTHE ASSIGNMENTThis is a running group assignment, which consist of four deliverables and a class activity. Due dates for eachdeliverable and the class activity are provided in the syllabus. The objectives of the assignment are for students topractice the writing of user stories and story maps, estimation using the Planning Poker technique, planning aSprint, track the project execution using Sprint and Release burndown charts and conduct a retrospective sessionin which suggestion for improvements are made.The expectation is that each submitted presentation will be of professional quality. Each report should contain atleast the output of the activities described for each of them. Besides its evaluation in terms of content, thedeliverables and the class activity will be graded on the basis of its overall organization, grammar, spelling andreadability. Submissions consist of a single PDF file named with the name of the group and the deliverable number.Students must structure the content so that is readable as a report. Image, html, disconnect files and zooming in orout of a gigantic one-page document are examples of things that will not be accepted. it important to revise andproofread the reports before they are submitted. At all times you must apply the reasonable person principle. Ifyou find yourself wondering if something is right or wrong it is safe to assume the latter.THE TIME REPORTING SYSTEMINTRODUCTIONYour company has won a contract to develop a Time Reporting System for nonexempt employees. The system isgoing to replace a legacy mainframe application with a more modern web based one.The system will be developed using Java and a yet undetermined relational database. It must also be able toexecute seamless on Internet Explorer and Firefox. The system will be deployed in AWS.SYSTEM DESCRIPTIONThe purpose of the Time Reporting System is to allow nonexempt employees of a firm report the hours worked indifferent projects so that customers could be billed and the employees paid. The client has offices in four differlocations across the country. The system’s users and its interface to other systems are depicted in Figure 1.The hours worked by employees are charged to standard categories called “pay codes”. Employees can only chargeto those pay codes and projects they have been authorized to do so by the supervisors. Employees must report thehours worked weekly which for historical reasons is called a “time sheet”. See Figure 2.As many of the firm’s employees work at their customers’ premises, the system must be able to be remotelyaccessed, preferably through a web interface to eliminate the need to install software on the employees’machines.To minimize the risk of accidental misuse or intentional tampering with the data, access to the system will bepassword protected and the creation of pay codes separated from the authorization to charge to them.Worked hours can be only approved by those supervisors who created the authorization to charge or theirdelegates. A supervisor cannot authorize himself to charge to a pay code.To minimize the risk of accidental misuse or intentional tampering with the data, access to the system will bepassword protected and the creation of pay codes separated from the authorization to charge to them.2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusWorked hours can be only approved by those supervisors who created the authorization to charge or theirdelegates. A supervisor cannot authorize himself to charge to a pay code. The initial list of user stories is given inTable 1.Figure 1. Context Diagram for the Time Reporting System2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusWeekly Employee Time Sheet for Week Ending: MM/DD/YYEmployee Name:Employee No:Supervisor:DayProjectTaskRegular d: MM/DD/YYApproved by xxxxxxxxx on MM/DD/YYFigure 2. Existing time sheet2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusTable 1. List of user stories identified during the initial meetings with the project ministrator1015ActionAuthorize employeesBlock employees fromtemporarily use thesystemReset an employeepasswordCreate pay temadministratorDelete pay codes30Any userLog in into the system35EmployeeReport working hours4045Asa(n)EmployeeEmployeeBenefitI can assure the integrity ofthe data reportedAssure the integrity of thedata reportedIwouldlike toSubmit reported hoursRecall reported hours50EmployeeProduce a report ofworked hours55SupervisorCreate a chargeauthorization60SupervisorApprove time sheet65SupervisorReject time sheet70SupervisorDelegate approval power75SupervisorRevoke a delegationsothatHelp people that forgot theirpasswordSo that the company cancapture hours intoappropriate categories whilepreserving the integrity of thedataSo that the company cancapture hours intoappropriate categories whilepreserving the integrity of thedataSo that he/she can use thesystemSo that I can log the hoursworkedSo that I will be paidSo that I can correct a mistakethat was not detected at thetime of data entrySo I can have a record of thehours worked in a givenperiodSo that employees only chargehours to those projects/tasksthey are authorized toSo I can control the numbersof hours reported by mysubordinatesSo I can control the numbersof hours reported by mysubordinatesSo I can designate an alternateto approve time sheets in caseI am unavailableTo terminate theauthorization for somebody toapprove time sheets on mybehalf2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusDELIVERABLE 1: USER STORIES AND STORY MAPThis part of the assignment focus on documenting the needs and want of the user. After the initial discussions thatled to the information provided in the introduction. The team needs to confirm their understanding and identifygaps and overlaps in the required functionality as well as to establish the look and feel of the new system.a.Draw a story map that includes the given user storiesb.Identify between three and five missing user storiesc.For two of the user stories above, create the conversation part of the story by interviewing a member ofanother team, your pick (In the report provide the name of the student you interviewed, and the number ofthe group that interviewed you). The conversation may include for example, specific data you want to capture,or some policy the use story needs to comply withd.Write the confirmation part of each user story (all of them)e.Create a wireframe diagram for two key user stories that could be used as a guideline for the look and feel ofthe other user storiesf.Create a notional architecture for the system. Introduce technical user stories and knowledge acquisitionstoriesg.Create the product backlog2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusDELIVERABLE 2: PLANNING POKER ESTIMATIONThis part of the assignment focuses on learning a well-known agile estimation technique: The planning poker.a.Estimate all user stories in story points. Provide a sheet with the final estimate for each user story by eachteam memberb.Estimate all technical and knowledge acquisition stories in ideal hoursc.Evaluate the internal consistency of the user stories’ estimationd.Given a budget of 900 hrs. decide on the feasibility of the project taking in consideration all the meetingsprescribed by Scrum, all the technical and knowledge acquisition stories and that 10% of the iteration effortought to be allocated to grooming the backloge.Update the backlog with the estimates2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)

Agile Development Frameworks: TheoryCMU SE 17604, Eduardo MirandaAssignment 1: Defining, planning and executing a Scrum projectDue: Dates shown on syllabusDELIVERABLE 3: SPRINT PLANNINGGiven the set of product owner preferences shown in Table 2 and assuming a sprint duration of two weeks, selecta number of stories (user, technical, knowledge acquisition) to complete during the same.a.Prepare a Sprint resource availability plan: discount time devoted to meetings, backlog grooming and otheron-going activities mandated by the processb.Discuss the initial velocity to be used for planningc.Prepare a detailed design (e.g. class diagram, sequence diagram) corresponding to the selected stories. Itshould provide enough understanding for the team to build itd.Create a dependency matrix at the class or method level to identify the development sequencee.Map the detailed design onto independent, individually assignable specific tasks, e.g. develop class Customer,develop mock object DB, develop test fixture for the Customer class, prepare user documentation, etc.f.Estimate each task above in ideal hours. Tasks shall be such that they can be completed by an individual inbetween 4 and 16 hours. Shorter tasks should be consolidated, longer tasks should be broken down.g.Iterate until the work the team will be committing to is doable within the Sprint time boxh.Create the Sprint backlogTable 2 Product owner preferencesLoginCreate Pay CodeCreate Charge AuthorizationSubmit reported hoursApprove time sheetReject a time sheet2017, Eduardo Miranda – licensed under Creative Commons Attribution 4.0 Int’l (CC BY 4.0)