Week 6, Discussion 6

In Scenario 3, you were required to develop a release plan for the first four months of a year-long project (or the full year, depending on your interpretation). Scenario 4 continues Scenario 3, but shifts from the high-level release level to the low-level estimation, sprint backlog, daily Scrum meeting, sprint burndown, and release burndown “rubber meets the road” level. You have two weeks to complete Scenario 4. Be sure you read over Scenario 4 carefully several times.

This week’s activities helps get you and your team focused on coming up to speed on some of the main concepts and practices you will need to master in Scenario 4. Your most helpful resources will be the Lecture Notes, assigned readings, and any additional web resources you may search out and choose to use.

For Discussion 6, the requirement is to develop a 100+ word post that summarizes the 3 main ways that sprint work efforts (workload) can be estimated from user stories: function points, storypoints, and estimated hours. Keep in mind that you will be using estimated hours (as provided) for Scenario 4 purposes.

Note: The knowledge and insight you gather from this review will be helpful for you in completing the exercises (parts) of Scenario 4. This Scenario 4, in a sense, culminates the planning/execution work cycle because Scenario 5 focuses on retrospectives, or looking back at what has been done and how it could have been done better. Scenario 4 is focused on giving students a first-hand insight into how work tasks (features) are developed within an Agile PM project.

Note: Content not coming directly from you will need to be cited per APA. FYI, best practice is to use citations to support your content and assertions.

Note: Responses may be a single paragraph or multi-paragraph, but should be well-organized, thorough, and well-presented.

Explanation & Answer length: 300 Words3 attachmentsSlide 1 of 3

  • attachment_1attachment_1
  • attachment_2attachment_2
  • attachment_3attachment_3

UNFORMATTED ATTACHMENT PREVIEW

The XYZ Corporation Agile Project Management Course Main Case UMGC IFSM 441 Introduction to Main Case and Scenario Assignments This is the Agile Project Management (IFSM 441) course main case. This case focuses on the XYZ Corporation, a fictitious but life-like corporation, and its project management environment. In conjunction with this case, students are assigned five assignment scenarios over the course of UMUC’s 8-week semester that extend the details of this main case and require students to apply and demonstrate their knowledge of Agile project management concepts. The five scenarios themselves are independent of each other, though each links back to the details of this main case. Each scenario requires students to perform one or more work tasks as if they are employees of the XYZ Corporation, according to the context and details specified in each scenario. Overview of XYZ Corporation and its Project Management Environment The XYZ Corporation is a large private-sector company headquartered in Adelphi, MD that focuses on government contracting. Approximately 80% of annual revenues stem from the federal government sector, 14 % from the state government sector, 5% from the local government sector, and 1% from the private sector. 2011 annual revenues for the corporation were close to $100M. XYZ has approximately 700 employees. XYZ Corporation focuses on three main service delivery areas: 1) emergency management, 2) health crisis prevention/response management, and 3) related logistical, coordination, and collaboration services. The corporation derives approximately 80% of its revenues from services and 20% from products (hardware, software, etc.). Approximately, 60% of delivered services are information technology services, 30% management consulting services, and the remaining 10% an assortment of training and other support services. Approximately, 90% of the revenue from products is Internet related, and the other 10% is a wide assortment of other products. The XYZ Corporation is made up of the following four divisions: 1) Information Technology and Processes (IT management, Project Management Office (PMO), etc. ; 2) Administration (Human Resources, Payroll, etc.); 3) Emergency Management Service/Product Delivery (Marketing, Sales, Client Relations, Strategic Planning, Product/Service Development, Product/Service Delivery, etc.); and 4) Health Crisis Prevention and Response Management Service/Product Delivery (Marketing, Sales, Client Relations, Strategic Planning, Product/Service Development, Product/Service Delivery, etc.). An organizational chart follows that illustrates how XYZ’s Project Management Office (PMO) provides project governance: 1 Instructor/Developer: Williams XYZ Corporation’s Project Management Office (PMO) promotes, develops, and maintains project methodologies and standards, and, as well, oversees all aspects of project implementation and governance for specified projects. The PMO at XYZ routinely supports 3 approved project management methodologies: 1) PMBOK-compliant Methodology (per PMI’s PMBOK and related best practices); 2) Agile Methodology (per the Agile PM (APM) Framework and Agile best practices); and 3) PMBOK/Agile Hybrid Methodology (a combination of PMBOK and Agile PM best practices). Most projects are hybrid. The PMO is responsible for determining not only which projects are approved, but, as well, which project management methodology will be employed for each approved project. The PMO routinely considers two main factors in pairing a methodology with a project: 1) internal unit fit for efficiency/effectiveness based on the use of methodologies in past projects, requests by unit managers, skills of available PMO/unit project managers, and other factors; and 2) external business environment factors, such as business/technical sector, uncertainty, complexity, competition/opportunity, timeframe, technologies/processes/staff involved, etc. This is the organization’s customized methodology adaption approach based on Agile PM best practices. By mandate of corporate policy, the PMO must be involved in all projects with over a $100,000 annual budget. All business units are encouraged to involve the PMO in projects as may be beneficial and per polices are required to involve PMO oversight in projects with over $100,000 annual budget. Internally, XYZ uses the PeopleSoft ERP across all divisions and an assortment of other Intranet and Internet applications built either on a Java or .NET platform. Additional XYZ Corporation PMO and Project Management Approaches Information The XYZ Corporation’s approaches to project management have been greatly influenced by PMI’s PMBOK approaches and, more recently, by 1) Agile PM and Agile approaches, and 2) concepts, best practices, and approaches of various Agile Manifesto signers and Agile PM luminaries. Let’s Scrum: How Scrum Methodology Encourages Students to View Themselves as Collaborators is authored by Rebecca Pope-Ruark, Michelle Eichel, Sarah Talbott and Kasey Thornton. What Every Owner Should Know is authored by Carlo Kruger. For more background information on the related best practice concepts and approaches of Agile PM luminaries, see the assigned readings or search the web. XYZ Corporation’s Agile project governance structures, methodologies, standards, and practices are greatly influenced by these sources and, as implemented, are centrally driven by the XYZ PMO in close collaboration with the Administration Division and the two Line of Business (LOB) Divisions. Summary This document has introduced the XYZ Corporation and its technology platforms and project management approaches of choice. Since you will be an “employee” of

Do you similar assignment and would want someone to complete it for you? Click on the ORDER NOW option to get instant services at essayloop.com

Do you have a similar assignment and would want someone to complete it for you? Click on the ORDER NOW option to get instant services at essayloop.com. We assure you of a well written and plagiarism free papers delivered within your specified deadline.