Week 10 Slides

pdf

School

The University of Sydney *

*We aren’t endorsed by this school

Course

5871

Subject

Information Systems

Date

Oct 30, 2023

Type

pdf

Pages

32

Uploaded by MateCaribou3742

Report
PMGT5871 Project Planning Week 10: Agile Projects using Scrum Framework Q: What is a product backlog?
Come prepared Mute your mic Turn on video Find a quiet place Be on time Have fun! Proposed Class Etiquette 4 When online When online When online
PMGT5871 Schedule Overview Day Topic Week 01 Introduction to the course Week 02 Plan Project Scope Week 03 Plan Project Time Week 04 Plan Project Cost and Quality Week 05 Plan a Project using MS Project Week 06 Plan Project HR and Procurement Week 07 Plan Project Risk Week 08 Plan Project Stakeholder Engagement and Communication Mid Semester break Week 09 Planning Agile Projects Week 10 Planning Agile Projects Week 11 Agile projects using Jira Week 12 Agile projects using Jira Week 13 Agile projects using Jira
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Scrum Framework
Scrum Artifacts Product Vision - The Product vision describes the purpose of a Product , the intention with which the Product is being created and what it aims to achieve for customers and users . -The Product vision describes a future state of the Product and what problems it tries to resolve or what ambitions it tries to fulfill. -The Vision summarizes the value to the customer of the change (aka the “ Value Proposition ”).
Product Vision
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Product Backlog – A list of features (new or changed), defects, issues, any required infrastructure and changes to deliver final product – Product backlog is source of truth for all requirements – Product backlog is updated regularly – If it is not in product backlog, it is not a requirement and not considered for delivery – Product backlog structure – Epic – Stories – Tasks – Sub-Task – Defects – Issues Scrum Artifacts
Scrum Artifacts Sprint Backlog – A list of deliverables in a timebound period – Sprint backlog is a subset of product backlog – It is only for specified time period – Stories in the sprint are completed with requirement details before sprint starts
Scrum Artifacts Epic – A series of user stories that share a broader strategic objective. – Epic is a large User Story , typically too big to be completed in a single Sprint. – First, the team will break the theme into several epics, which are themselves smaller strategic plans – Then, you must break down each epic further into user stories. – A story represents a small unit of development work that will allow a user to complete a task or goal in the product. – The Scrum Core Team can use a range of other tools to create efficient Epics such as: User Story Workshops Focus Group Meetings Questionnaires
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Epics – Personas Personas are supplementary to Epics in that they help the team better understand users and their requirements and goals. Personas are highly detailed fictional characters that represent the majority of users and other stakeholders who may not directly use the end product. Personas are created to identify the needs of the target user base . Creating specific Personas can help the team better understand users and their requirements and goals. Based on a Persona, the Product Owner can more effectively prioritise features to create the Prioritised Product Backlog.
Creating a Personas A persona can include the following items: A fictional name and preferably a picture, like a stock image, to the character. Highly specific attributes such as age, gender, and education. The persona’s environment, interests, and goals. A quote illustrating the Persona’s requirements can be included as well.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Personas Example Matty Fishburne: 28 years old, Sales Manager for a small, but extremely busy courier company. “I never have a spare minute to myself during the day so I do all my shopping on-line. I know what I want and I like to jump on-line, order, and get out again.” Matty is a 28-year-old Sales Manager who works 10 hours a day. Matty has a wide circle of friends and a large family. He is very generous and loves buying gifts for special occasions such as birthdays, anniversaries, new houses, etc. Although time-poor, Matty is thoughtful and always likes to give gifts that he knows will be appreciated. Matty doesn’t like to visit stores and does his shopping on-line whenever possible. Quote persona’s environment, interests
•Create 5 Personas for your Case study ACTIVITY – 10 mins
Scrum Artifacts User Story – A user story is the smallest unit of work in an agile framework. It’s an end goal, not a feature, expressed from the software user’s perspective. – It is a brief statement of a functional product need from a specific type of user. User story is written in an informal general expression. Each user story is to define only one functionality with acceptance criteria.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
User Story Template User stories are often expressed in a simple sentence, structured as follows: “As a [persona], I [want to], [so that] + Acceptance Criteria” Breaking this down: • "As a [persona]": Who are we building this for? We understand how that person works, how they think and feel. • “Wants to”: Here, we’re describing their intent — not the features they use. What is it they’re trying to achieve? This statement should be implementation free — if you’re describing any part of the UI and not what the user goal is you're missing the point. • “So that”: How does their immediate desire to do something this fit into their bigger picture? What’s the overall benefit they’re trying to achieve? What is the big problem that needs solving? • “Acceptance Criteria”: Definition of Done
Acceptance Criteria Every User Story has associated Acceptance Criteria. User Stories and Epics are subjective, so the Acceptance Criteria provide the objectivity required for the User Story to be considered as Done or not Done during the Sprint Review providing clarity to the Team on what is expected from a User Story. Acceptance criteria can be writing as bullet points or using the following formats: Format 1… When <<an event occurs>>, then <<this is what should happen>> When a user selects an item, then the item is added to the cart. When an item is added to the cart, then total cost of the cart is updated. Format 2… Given…<<precondition>> When…<<event>> Then…<<expected change>>
User story example
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
User story example
User story example
•Write at least three user stories for the case study project (including acceptance criteria) ACTIVITY – 15 mins
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
INVEST model to create better User Stories Independent Each User Story should be independent of one another to support estimation and prioritization. Negotiable A User Story should leave opportunities for conversation or negotiation with the customer. A Story card should contain a short description without too many details. Valuable Every Story must be of value to the customer. To ensure a Story is valuable, the customer should be involved in writing the Story. Estimatable A Story should be written in a way that developers can easily estimate it. This will help prioritization and planning. Small A well-written Story should be small in effort (no more than three people-weeks of effort). If more effort is required, there is high probability of estimation and scoping errors. Testable Anything that cannot be tested should not be developed. If it cannot be tested, then it cannot be confirmed as Done.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Story size estimation – Story Sizing or Estimation – Stories are estimated for work and assigned sizing or points – Estimation does include work, complexity, time and other factors – Estimation is relevant to the team, sprint and complexity of the work – It means a number 5 in one team and a number 5 in another team may not be equal – Estimations are made based on – T-Shirt size (S, M, L, XL) – Fibonacci sequence (1, 2, 3, 5, 8, 13, ….) – Planning poker
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Planning Poker Is an agile estimating and planning technique that is consensus based. 1 Customer/Product Owner reads story 2 Team Estimates 3 Team discusses 4 Team Estimates again
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Planning Poker Product Owner describes requirement Developers ask questions Each developer chooses a card Cards flipped over when everyone ready Point value agreement Value Noted Discussion New Requirement Point value disagreement
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
•In your teams, Estimate the size of the user stories created previously. ACTIVITY – 10 mins
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Backlog It is prioritized to ensure that the team builds the most important features first It is estimated by the team to give the product owner clarity and enabling them to answer questions such as "When will these stories be done?" It includes all the work necessary to complete the project It is constantly changing and evolving to reflect the current realities of the project
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Value-based Prioritization • The Scrum framework is driven by the goal of delivering maximum business value in a minimum time span. • One of the most effective tools for delivering the greatest value in the shortest amount of time is prioritization. • Scrum aims at delivering a valuable product or service to the customer on an early and continuous basis. While prioritizing requirements in the Prioritized Product Backlog, the following three factors are considered:
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Backlog Prioritization techniques MoSCoW method – Contingency built in KANO Analysis
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Backlog Prioritization techniques Paired Comparison: Each User Story in the backlog is taken individually and compared with the other User Stories in the list, one at a time. Each time two User Stories are compared, a decision is made regarding which of the two is more important. 100-point method: Each group member is given 100 points which they then allocate to the User Stories, giving more points to those they feel are more important.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
•In your teams, prioritise the user stories created previously. ACTIVITY – 10 mins
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Questions
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help

Related Documents

Assessment-1-ICTSAS502.docx
Assessment 3 ICTSAS502 .docx
A Woman Wearing a Black Hijab · Free Stock Photo.pdf
global business platforms .docx
How to navigate to Netacad Shell for reading materials and exams-2.docx
AT3-FINALfah.docx
HLTH 303- sept 12.docx
ICTSAS526_ASSESSMENT1.pdf
31272 Project Management and the Professional.pdf
DIPLOMA OF INFORMATION TECHNOLOGY ASSESSMENT 3.docx
Screenshot 2023-10-23 at 6.48.25 PM.png
assessment 3 Case Study _Kanjanaporn.docx

Browse Popular Homework Q&A

Q: How many double bonds are present in Blue No. 1? (Include the S=O double bonds).
Q: Constant amount of ideal gas is kept inside a cylinder by a piston. Then the gas expands…
Q: CREATE TABLE BOOK STORES ( Store ID NUMBER(8) NOT NULL, Name VARCHAR2(30) UNIQUE NOT NULL, Contact…
Q: 4.) f(x) = HOLE(S) x³+4x²-21x x²+4x-21 VERTICAL HORIZONTAL ASYMPTOTE(S) ASYMPTOTE -10 SLANT…
Q: After Hurricane Maria, hundreds of nonprofit organizations streamed to Puerto Rico and other…
Q: What are two main keywords or phrases that would be helpful in locating information about this…
Q: Use Newton's Method to approximate the zero(s) of the function. Continue the iterations until two…
Q: Consider the algorithm for insertion sort shown below. The input to this algorithm is an array A.…
Q: Structure- Data! Redraw Original Structure and Add Lone Pairs Redraw Original Structure with Lone…
Q: is) In your drawer, you have 7 pairs of different socks, all mixed together. In total dark- ness,…
Q: Use a software program or a graphing utility with matrix capabilities to find the transition matrix…
Q: Tile Corporation sells 600 units at a selling price of $800 per unit. Tile's variable expense…
Q: Consider the following table. X f(x) X f(x) 0.0 6.5 2.0 7.9 0.4 6.1 2.4 8.5 0.8 6.4 2.8 8.6 1.2 6.6…
Q: 2. A rollerskate is dragged across the ground for 3.4 meters, by someone pulling on its shoelace.…
Q: Ho:μ = 24 Ha: # 24 x = 27.2, n = 56, o = 8.46, a = .01 a. Use the data given to test the following…
Q: Six hundred kilograms​ [kg] of paint solvent will be stored to remove the paint display on the…
Q: What is the molarity (M) of the aqueous solution that contains 3 g of LiNO, in 170 mL of solution?
Q: 6B1: Recognize and apply the pathway of syn addition with larger atoms via three-membered transition…
Q: Suppose that round ears in guinea pigs is a recessive phenotype. You have just adopted a guinea pig…
Q: a. Compute the mean and standard deviations for each of the tire pressure columns. b. Draw or create…
Q: Young's modulus for compression of human bone is approximately 9x10⁹ N/m^2. Assume that a femur has…
Q: use bernoulli, Solve for y Jy + by dy dx J
Q: Use the graphs shown in the figure below. All have the form f (x) = ab° BA D E F Which graph has the…
Q: * 12-1 y
Q: 27) (1-1) (Hint: (1-²)→ Ỹ n=1 N.N →1/e