{"id":664,"date":"2024-12-14T04:19:31","date_gmt":"2024-12-14T04:19:31","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/?post_type=chapter&p=664"},"modified":"2025-01-23T02:45:52","modified_gmt":"2025-01-23T02:45:52","slug":"12-7-exercises","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/chapter\/12-7-exercises\/","title":{"rendered":"12.7 Exercises"},"content":{"raw":"
\r\n

Exercise 1: <\/strong>Scrum for a Retail Mobile Application<\/h2>\r\n<\/header>\r\n
\r\n\r\nRetailPro, an imaginary e-commerce company specializing in home goods, is transitioning to a mobile-first approach to enhance customer engagement and sales. The company\u2019s leadership has decided to develop a new mobile application to support its business goals. The project team has adopted the Scrum framework to ensure a flexible, collaborative, and iterative development process. The product will be launched in three months, and the team is in its first Sprint.\r\n

Project Details:<\/h3>\r\nProduct Goal:<\/strong> Develop a user-friendly mobile application enabling customers to browse, search, and purchase products efficiently while offering personalized recommendations based on purchase history.\r\n\r\nSprint Goal for the First Sprint:<\/strong> Implement a basic user management system, allowing customers to register, log in, and reset their passwords.\r\n\r\nTeam Structure:<\/strong>\r\n
    \r\n \t
  • Product Owner: Responsible for prioritizing the Product Backlog and ensuring the team delivers value to stakeholders.<\/li>\r\n \t
  • Scrum Master: Responsible for facilitating the Scrum process, removing impediments, and coaching the team.<\/li>\r\n \t
  • Developers: A cross-functional team of 6 developers with expertise in front-end, back-end, and database design.<\/li>\r\n<\/ul>\r\nSprint Details:<\/strong>\r\n
      \r\n \t
    • Duration: 2 weeks<\/li>\r\n \t
    • Sprint Backlog:\r\n
        \r\n \t
      1. User Story: \u201cAs a new user, I want to register an account so that I can save my payment details for future use.\u201d (5 Story Points)<\/li>\r\n \t
      2. User Story: \u201cAs a returning user, I want to log in using my email and password to access my account.\u201d (3 Story Points)<\/li>\r\n \t
      3. User Story: \u201cAs a user, I want to reset my password if I forget it so that I can regain access to my account.\u201d (2 Story Points)<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ul>\r\nTools and Metrics:<\/strong>\r\n\r\nTools: Atlassian Jira for task tracking, Zoom for meetings, and Figma for UI design.\r\n\r\nMetrics: Burndown Chart for Sprint progress, Velocity Chart for long-term planning.\r\n

        Key Events During the Sprint:<\/h3>\r\nSprint Planning:<\/strong> The team discussed the user stories, identified dependencies, and defined the Sprint Goal. Tasks were broken into smaller subtasks, such as creating a database schema for user management and implementing a password validation system.\r\n\r\nDaily Scrum:<\/strong> Team members shared updates:\r\n
          \r\n \t
        • \u201cYesterday, I completed the registration form UI. Today, I\u2019ll integrate it with the database.\u201d<\/li>\r\n \t
        • \u201cI\u2019m working on email verification for password resets. I\u2019ve hit an issue with the SMTP server configuration.\u201d<\/li>\r\n \t
        • Impediment: The SMTP server for email verification was misconfigured, delaying progress. The Scrum Master coordinated with the IT team to resolve the issue within a day.<\/li>\r\n<\/ul>\r\nSprint Review:<\/strong> The team demonstrated the completed user registration and login features. Stakeholders suggested adding password strength indicators to enhance usability.\r\n\r\nSprint Retrospective:<\/strong>\r\n
            \r\n \t
          • What went well: Collaboration among developers was seamless, and the burndown chart showed steady progress.<\/li>\r\n \t
          • What didn\u2019t go well: The team underestimated the complexity of the password reset feature.<\/li>\r\n \t
          • Action items: Allocate more time for complex features and improve dependency identification during Sprint Planning.<\/li>\r\n<\/ul>\r\n

            Questions:<\/h3>\r\n

            Part 1: General Understanding of the Scrum Process<\/strong><\/h4>\r\n
              \r\n \t
            1. What is the primary responsibility of the Product Owner in this project?<\/li>\r\n \t
            2. What is the main role of the Scrum Master during the Sprint?<\/li>\r\n \t
            3. Describe the Sprint Goal for the first Sprint in this project.<\/li>\r\n<\/ol>\r\n

              Part 2: Sprint Planning and Execution<\/strong><\/h4>\r\n
                \r\n \t
              1. Assign a priority to each user story based on its importance to the Product Goal.<\/li>\r\n \t
              2. During Sprint Planning, the team broke down user stories into smaller subtasks. Provide an example of a subtask for implementing the password reset feature.<\/li>\r\n \t
              3. How did the team identify and handle dependencies during Sprint Planning?<\/li>\r\n<\/ol>\r\n

                Part 3: Monitoring and Metrics<\/strong><\/h4>\r\n
                  \r\n \t
                1. How do these tools used to track the team\u2019s progress contribute to achieving the Sprint Goal?<\/li>\r\n \t
                2. How does a Burndown Chart help the team monitor Sprint's progress?<\/li>\r\n \t
                3. Why is the Velocity Chart useful for long-term planning in Scrum?<\/li>\r\n<\/ol>\r\n

                  Part 4: Sprint Events<\/strong><\/h4>\r\n
                    \r\n \t
                  1. During the Daily Scrum, one team member mentioned hitting an issue with the SMTP server configuration. How did the Scrum Master address this impediment?<\/li>\r\n \t
                  2. How can the feedback from stakeholders during the Sprint Review be integrated into future Sprints?<\/li>\r\n \t
                  3. What is the importance of demonstrating completed features during the Sprint Review?<\/li>\r\n<\/ol>\r\n

                    Part 5: Retrospective and Continuous Improvement<\/strong><\/h4>\r\n
                      \r\n \t
                    1. How can action items be addressed in future Sprints?<\/li>\r\n \t
                    2. How might the team adjust their approach to Sprint Planning based on the retrospective action items?<\/li>\r\n \t
                    3. What went well during the Sprint, and how can the team ensure these positive aspects are maintained in future Sprints?<\/li>\r\n<\/ol>\r\n

                      Part 6: Critical Thinking<\/strong><\/h4>\r\n
                        \r\n \t
                      1. If the password reset feature's complexity was underestimated, what strategies could the team use to prevent similar underestimations in the future?<\/li>\r\n \t
                      2. Imagine the stakeholders request a new feature (e.g., adding biometric login functionality) during the Sprint. How should the team handle this request according to Scrum principles?<\/li>\r\n \t
                      3. How might delays in resolving impediments (e.g., the SMTP server issue) impact the Sprint Goal and overall project timeline?<\/li>\r\n<\/ol>\r\n

                        Part 7: Scenario-Based Questions<\/strong><\/h4>\r\n
                          \r\n \t
                        1. If the burndown chart shows inconsistent progress halfway through the Sprint, what might this indicate, and how should the team address it?<\/li>\r\n \t
                        2. Suppose the password strength indicator suggested by stakeholders needs additional development time. How can the Product Owner prioritize this feedback while ensuring the team remains focused on the Sprint Goal?<\/li>\r\n<\/ol>\r\n<\/div>\r\n<\/div>","rendered":"
                          \n
                          \n

                          Exercise 1: <\/strong>Scrum for a Retail Mobile Application<\/h2>\n<\/header>\n
                          \n

                          RetailPro, an imaginary e-commerce company specializing in home goods, is transitioning to a mobile-first approach to enhance customer engagement and sales. The company\u2019s leadership has decided to develop a new mobile application to support its business goals. The project team has adopted the Scrum framework to ensure a flexible, collaborative, and iterative development process. The product will be launched in three months, and the team is in its first Sprint.<\/p>\n

                          Project Details:<\/h3>\n

                          Product Goal:<\/strong> Develop a user-friendly mobile application enabling customers to browse, search, and purchase products efficiently while offering personalized recommendations based on purchase history.<\/p>\n

                          Sprint Goal for the First Sprint:<\/strong> Implement a basic user management system, allowing customers to register, log in, and reset their passwords.<\/p>\n

                          Team Structure:<\/strong><\/p>\n

                            \n
                          • Product Owner: Responsible for prioritizing the Product Backlog and ensuring the team delivers value to stakeholders.<\/li>\n
                          • Scrum Master: Responsible for facilitating the Scrum process, removing impediments, and coaching the team.<\/li>\n
                          • Developers: A cross-functional team of 6 developers with expertise in front-end, back-end, and database design.<\/li>\n<\/ul>\n

                            Sprint Details:<\/strong><\/p>\n

                              \n
                            • Duration: 2 weeks<\/li>\n
                            • Sprint Backlog:\n
                                \n
                              1. User Story: \u201cAs a new user, I want to register an account so that I can save my payment details for future use.\u201d (5 Story Points)<\/li>\n
                              2. User Story: \u201cAs a returning user, I want to log in using my email and password to access my account.\u201d (3 Story Points)<\/li>\n
                              3. User Story: \u201cAs a user, I want to reset my password if I forget it so that I can regain access to my account.\u201d (2 Story Points)<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n

                                Tools and Metrics:<\/strong><\/p>\n

                                Tools: Atlassian Jira for task tracking, Zoom for meetings, and Figma for UI design.<\/p>\n

                                Metrics: Burndown Chart for Sprint progress, Velocity Chart for long-term planning.<\/p>\n

                                Key Events During the Sprint:<\/h3>\n

                                Sprint Planning:<\/strong> The team discussed the user stories, identified dependencies, and defined the Sprint Goal. Tasks were broken into smaller subtasks, such as creating a database schema for user management and implementing a password validation system.<\/p>\n

                                Daily Scrum:<\/strong> Team members shared updates:<\/p>\n

                                  \n
                                • \u201cYesterday, I completed the registration form UI. Today, I\u2019ll integrate it with the database.\u201d<\/li>\n
                                • \u201cI\u2019m working on email verification for password resets. I\u2019ve hit an issue with the SMTP server configuration.\u201d<\/li>\n
                                • Impediment: The SMTP server for email verification was misconfigured, delaying progress. The Scrum Master coordinated with the IT team to resolve the issue within a day.<\/li>\n<\/ul>\n

                                  Sprint Review:<\/strong> The team demonstrated the completed user registration and login features. Stakeholders suggested adding password strength indicators to enhance usability.<\/p>\n

                                  Sprint Retrospective:<\/strong><\/p>\n

                                    \n
                                  • What went well: Collaboration among developers was seamless, and the burndown chart showed steady progress.<\/li>\n
                                  • What didn\u2019t go well: The team underestimated the complexity of the password reset feature.<\/li>\n
                                  • Action items: Allocate more time for complex features and improve dependency identification during Sprint Planning.<\/li>\n<\/ul>\n

                                    Questions:<\/h3>\n

                                    Part 1: General Understanding of the Scrum Process<\/strong><\/h4>\n
                                      \n
                                    1. What is the primary responsibility of the Product Owner in this project?<\/li>\n
                                    2. What is the main role of the Scrum Master during the Sprint?<\/li>\n
                                    3. Describe the Sprint Goal for the first Sprint in this project.<\/li>\n<\/ol>\n

                                      Part 2: Sprint Planning and Execution<\/strong><\/h4>\n
                                        \n
                                      1. Assign a priority to each user story based on its importance to the Product Goal.<\/li>\n
                                      2. During Sprint Planning, the team broke down user stories into smaller subtasks. Provide an example of a subtask for implementing the password reset feature.<\/li>\n
                                      3. How did the team identify and handle dependencies during Sprint Planning?<\/li>\n<\/ol>\n

                                        Part 3: Monitoring and Metrics<\/strong><\/h4>\n
                                          \n
                                        1. How do these tools used to track the team\u2019s progress contribute to achieving the Sprint Goal?<\/li>\n
                                        2. How does a Burndown Chart help the team monitor Sprint’s progress?<\/li>\n
                                        3. Why is the Velocity Chart useful for long-term planning in Scrum?<\/li>\n<\/ol>\n

                                          Part 4: Sprint Events<\/strong><\/h4>\n
                                            \n
                                          1. During the Daily Scrum, one team member mentioned hitting an issue with the SMTP server configuration. How did the Scrum Master address this impediment?<\/li>\n
                                          2. How can the feedback from stakeholders during the Sprint Review be integrated into future Sprints?<\/li>\n
                                          3. What is the importance of demonstrating completed features during the Sprint Review?<\/li>\n<\/ol>\n

                                            Part 5: Retrospective and Continuous Improvement<\/strong><\/h4>\n
                                              \n
                                            1. How can action items be addressed in future Sprints?<\/li>\n
                                            2. How might the team adjust their approach to Sprint Planning based on the retrospective action items?<\/li>\n
                                            3. What went well during the Sprint, and how can the team ensure these positive aspects are maintained in future Sprints?<\/li>\n<\/ol>\n

                                              Part 6: Critical Thinking<\/strong><\/h4>\n
                                                \n
                                              1. If the password reset feature’s complexity was underestimated, what strategies could the team use to prevent similar underestimations in the future?<\/li>\n
                                              2. Imagine the stakeholders request a new feature (e.g., adding biometric login functionality) during the Sprint. How should the team handle this request according to Scrum principles?<\/li>\n
                                              3. How might delays in resolving impediments (e.g., the SMTP server issue) impact the Sprint Goal and overall project timeline?<\/li>\n<\/ol>\n

                                                Part 7: Scenario-Based Questions<\/strong><\/h4>\n
                                                  \n
                                                1. If the burndown chart shows inconsistent progress halfway through the Sprint, what might this indicate, and how should the team address it?<\/li>\n
                                                2. Suppose the password strength indicator suggested by stakeholders needs additional development time. How can the Product Owner prioritize this feedback while ensuring the team remains focused on the Sprint Goal?<\/li>\n<\/ol>\n<\/div>\n<\/div>\n","protected":false},"author":256,"menu_order":8,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-664","chapter","type-chapter","status-publish","hentry"],"part":358,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/664","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/users\/256"}],"version-history":[{"count":8,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/664\/revisions"}],"predecessor-version":[{"id":1211,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/664\/revisions\/1211"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/parts\/358"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/664\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/media?parent=664"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapter-type?post=664"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/contributor?post=664"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/license?post=664"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}