Demonstrate core concepts of agile methodology

Assignment Help Project Management

Reference no: EM133743720 , Length: word count:2500

Assessment - Agile Case Study Report

Learning Outcome 1: Discuss and demonstrate core concepts of agile methodology within a context of a business case study.

Learning Outcome 2: Communicate the benefits of an agile PM plan in the context of a business case to demonstrate a response to a complex business need while aligning strategies to business priorities defined by changing business requirements.

Learning Outcome 3: Develop and communicate a collaborative strategy which embodies the principles of agile methodology to stakeholders of an organisation.

Part A: In-class Group Presentation (Progressive Elaboration Stage Gate A)

Every team member will be required to take an active part in the presentation. Team members who are NOT present or do NOT participate will NOT qualify for any marks.
There is a very specific and tight time limit of 10 minutes for this presentation. This is to ensure that the presentation is clean, clear and focused.
There is no need to provide basic agile definitions in this presentation as your audience already understands them.
Your team is expected to deliver the presentation as outlined below (you can provide additional slides if needed, just make sure the presentation stays within 10 minutes):
Slide 1 - The title slide must include the following information: Subject code, subject name, assessment number & title, students' names, students' numbers, enrolled program (e.g., Master of Business Information Systems), class CRN and learning facilitator's name.
Slide 2 - Provide pictures of team members and their names. During the presentation, introduce the team members.
Slide 3 - A description of the digital product you have chosen. Consider creating a unique name for your digital product and explain the project's purpose.
Slide 4 - The first version of your product vision statement.
Slide 5 - The list of features (only functional requirements) present in the first release of your digital product. There is NO requirement to include user story statements, just provide a name for each feature. Explain WHY you have chosen these features as the most important ones and explain WHAT the specific benefit each feature offers to users.
Note: For the first release, skip the basic features like Login, Payment, Notifications, Account Management, Helpline, etc. Instead, concentrate on the exciting and important features that will make users want to use your digital product.
Slide 6 - The list of features (only functional requirements) that your group plans to incorporate into the subsequent releases of your digital product following the first release.
Slide 7 - The specific sequence as well as the timeline in which your group plans to release all product features for the next FOUR quarters.
Slide 8 - Bibliography. A bibliography is a list of sources used in research or consulted for the content, to provide credibility and allow for further exploration by the audience.

Part B: In-class Group Presentation (Progressive Elaboration Stage Gate B)

Every team member will be required to take an active part in the presentation. Team members who are NOT present or do NOT participate will NOT qualify for any marks.
Remember! Once Part A is finished, your team should continue working weekly and identify additional features for your digital product in Part B. Your digital product should be more comprehensive compared to Part A.
All epics, features and stories must be consistently named in the MVP, mock-ups, product backlog, story cards, product roadmap, and release plan.
There is NO need to provide basic agile definitions in this presentation as your audience already understands them.
There is a time limit of 20 minutes for this presentation. This is to ensure that the presentation is clean, clear and focused.
The following concepts will need to be covered based on the case study (you can provide additional slides if needed, just make sure the presentation stays within 20 minutes):
Slide 1 - Title page. The title slide must include the following information: Subject code, subject name, assessment number & title, students' names, students' numbers, enrolled program (e.g., Master of Business Information Systems), class CRN, and learning facilitator's name.
Slide 2 - Team Members. Provide pictures of team members and their names. During the presentation, introduce the team members and explain the project's purpose. Remember to add the unique name of your digital product.
Slide 3 - Product Vision Statement. The product vision using the Product Vision Statement.
Slide 4 - Persona. Primary persona/s (no more than 2) of your digital product. Focus on identifying the primary persona. Based on your persona, explain WHY they are the main target users of your digital product and HOW your personas can assist your team in identifying the MVP features. You need to use a digital tool to create the personas, some free tools for this purpose include miro.com, xtensio.com, figma.com etc.
Slide 5 - Minimum Viable Product (MVP). Find the MVP for your digital product. Explain HOW MVP connects to the way you prioritised your product backlog items.
Note: For MVP, skip the basic features like Login, Payment, Notifications, Helpline, etc. Instead, concentrate on the exciting and important features that make users want to use your product.
Slide 6 - Mock-up. Low-fidelity screen mock-ups of your digital product. Use a digital tool like figma.com to create the mock-ups. All features of the MVP need to be depicted in the mock-ups.
Note: Each mock-up screen MUST include a figure caption clearly stating which MVP feature it represents.

Slide 7 - Product Backlog. Create a table that lists your product backlog items.
The product backlog should include a list of a minimum of 20 epics or features.
All backlog items must be prioritised from highest importance (must-have) to lowest
importance (won't-have) by using the MoSCoW technique.
All ‘Must-have' and ‘Should-have' backlog items need to be broken down for more details, employing a process known as story splitting or story decomposition.
All backlog items need to have estimated story points.
Note: When using story splitting or decomposition technique, provide only a brief name for each user story. You don't need to provide the user story statement in the product backlog.
Slide 8 - Story Cards. Choose ONE epic or feature with a ‘Must-Have' priority from the backlog. Demonstrate how to use the story card technique by creating story cards for all the user stories related to the selected epic or feature. Each story card should include the following items:
The user story statement (As a ... I want ..., so that ...).
Acceptance criteria using either the test-driven development or the behaviour-driven development (gherkin) techniques.
Slide 9 - Definition of Done. A list of criteria for determining the definition of done.
Slide 10 - Product Roadmap. Your product roadmap for all backlog items that you plan to add in sequence for the next FOUR quarters.
Note: Review your product backlog to ensure that you do not have sequencing or prioritisation mismatches. Consider the end of the current trimester as the start of the product roadmap.
Slide 11 - Release Planning. Your release plan for the next SIX months. Review the release plan to ensure that your release planning is aligned with the product roadmap.
Slide 12 - Agile Ceremonies. Your recommendations for setting up your Agile Ceremonies and cadence, explain which ceremonies have been selected and why. You need to identify the duration of your project sprint here so you can plan your Agile ceremonies accordingly.
Remember: Do NOT provide basic agile ceremonies definitions here.
Slide 13 - Agile Estimation. Your planned approach for estimating story points. Also, calculate the team's estimated velocity.
Remember: Do NOT provide story point or team velocity definitions here.
Slide 14 - Agile Reporting. Explain which reports or charts you will utilise to present the team's progress and how they will be employed.
Remember: Do NOT provide any chart or report explanation here.
Slide 15 - Bibliography. A bibliography is a list of sources used in research or consulted for the content, to provide credibility and allow for further exploration by the audience.

Part C: Final Group Report

The Presentation Part B is a summary of the contents of this report. Equally, you will receive feedback at the close of your presentation to ensure that you have not missed anything important and that you have an opportunity to act on key feedback. Your final group report MUST share more detailed information that explains how you responded to the case study.
The team is required to write a 2500-word report, the report must be related to the case study and is NOT a general discussion on agile project management.
A copy of the Team Contract MUST be included in the appendices.
A snapshot of each week's Kanban Board from Week 5 to Week 10 (a minimum of six snapshots) MUST be included in the appendices.
Please write a group report following the structure outlined below:
Title Page: The title page must include the following information: Subject code, Subject name, Assessment number & title, Students' names, Students' numbers, Enrolled program (Master of
...), class CRN, Learning facilitator's name.
The Table of Contents: Create a Table of Contents, using headings and subheadings, along with page numbers. This will make the organization of topics clear and let MS Word generate it automatically.
Remember: The table of contents starts on a new page.
Introduction: will serve as your statement of purpose for the report. This means that you will tell the reader what you are going to cover in your report. You will need to inform the reader of:
Your area of research and its context.
The key concepts you will be addressing.
What the reader can expect to find in the body of the report.

Body of the report: Ensure you refrain from offering elementary definitions, as they won't earn any marks. The following areas MUST be written based on the case study by using the information provided in Part B of this assessment:
Product Vision Statement
Product Roadmap
Release Planning
Lean Startup Tools used in Agile (Persona/s, MVP, and Mock-ups)
Agile Requirements (Product Backlog, Story Cards, and Definition of Done)
Agile Estimation (Story point and team velocity estimation methods)
Agile Reporting (explain the chosen reports/charts, why and how)
Agile Ceremonies and Cadence

Referencing.

Note: Need only Part 3.

Reference no: EM133743720

Questions Cloud

What are the possible immediate risks : Consider these questions: What are the possible immediate risks? What are the long-term consequences? How was information about this country gathered?

Major security challenges and vulnerabilities : Evaluate the purpose, structure, and design of base layer 1 of the Bitcoin network, which provides the security layer - demonstrate your proficiency

Identify the patient family or group you intend to work with : Summarize the problem you'll explore. Identify the patient, family, or group you intend to work with during your practicum.

Provides a perfect opportunity to set and accomplish goals : Setting and achieving goals is essential to success. Being a graduate student provides a perfect opportunity to set and accomplish goals.

Demonstrate core concepts of agile methodology : Discuss and demonstrate core concepts of agile methodology within a context of a business case study and demonstrate a response to a complex business need

What is the main point of the armstrong and hamilton reading : What is the main point of the Armstrong and Hamilton reading? How do they show that colleges might be reproducing rather than ameliorating inequality?

How would you respond to an invitation from a friend : How would you respond to an invitation from a friend to invest in a real estate venture that depends on uncertain future demand and interest rates?

Create an assessment of the familys presenting problem : Create an assessment of the family's presenting problem that incorporates what you learned in the other parts of the homework.

Write down some of the specific work job and career goals : Write down some of the specific work, job, and career goals that you have for the next 20, 10, and 5 years. Be as concrete and specific as possible.

User Account

All Pages