Question:

Undertake the role of "Product Owner", and identifyat least ten (10) Product Backlog Items (PBIs)for the following (below) case.

Case: CTA App. Develop a web application that communicates with the central data center of the Chicago public transit (CTA) system. The web application should provide real-time updates of bus and train schedules, locations, and time until arrival/departure. The first release for this application is roughly planned for 2-3 months from today

Assume that you have a fully capable agile team with all necessary skills to complete project work.

Requirement:

• Each Product Backlog Item must:
  • Be written in a user story format (e.g., "As a I want to so that ") and satisfy INVEST criteria (don't forget the "V" - items must be "Valuable" and be related to the Project Vision)
  • Be assigned a relative size (i.e., planning poker or "story point" estimates) - actual estimates are only used for the sprint backlog (the next assignment)
  • NOT be tasks - tasks belong in the sprint backlog (the next assignment)
  • The "Acceptance Criteria" column DOES NOT need to be completed (may be left blank). For practice, you may want to enter some details in this column.
• The Product Backlog must satisfy DEEP characteristics (especially the "P" - "prioritized")
  • The "Importance" column is how you identify the priority for each item with "1" = highest priority.

Expectations:

• At least 10 items listed satisfying the INVEST criteria
• All items phrased in the correct format. Needed format: Correct: "As a I want to so that ". Example: As a site member, I want to login so I can access subscriber content.
• All items are assigned a plausible and valid relative size. Needed: Assigned a relative size that is both plausible (i.e., realistic) and valid (i.e., 1, 2, 3, 5, 8, 13, 20, 40, or ).
• All items are prioritized correctly. Needed: The "Importance" column is used to identify the priority of each item (i.e., 1, 2, 3, ...) with "1" = highest priority or most urgent to complete; highest priority items should be "sprint ready" (i.e., can be completed in a single sprint or likely have relative sizes of 1, 2, 3, 5 rather than sizes of 13, 20, 40); no duplicates exist (i.e., two #1's, three #3's, etc.)