Team Name

Public Repo for --Team Name-- team @ --Organization Name-- bootcamp

Part 1

Team Name

--Team Name--

Git Repo

https://github.com/atilsamancioglu/ScrumBootcampTemplate

Team Roster

John Doe: Product Owner
Jane Doe: Scrum Master
Atil Samancioglu: Team Member/Developer

Product Name

--Product Name--

Far Vision

Movie App
- Description – This is a movie app listing movies from a main API along with the director, rating, year and many information as well as availability in popular streaming platforms such as Netflix, Prime etc.

Near Vision

IMDB Rating & Information
- Description – People can easily see the details of IMDB related data for their selected movie
Streaming platform availability
- Description – People can see whether they are available on their subscribed streaming platforms

Stakeholders

Movie Lovers
- People often spending their free times watching movies and criticizing them
Time fillers
- People needing a way to kill time for weekends
Cinema party groups
- Group of people trying to make an informed decision on their movie choice for their cinema & pizza party

User Persona

Zeynep is a white collar employee who is working hard on weekdays and goes out at most couple of days during week. However at weekends she wants to watch a movie at night in her home but she has no idea what Neflix is offering and whether the movies are good enough to watch.
- Age
  - 34
- Gender
  - Female
- educational background
  - Undergraduate Level Credentials
- Marital Status
  - Married
- Profession
  - Senior sales executive
- Work experience years & level of expertise
  - 10 years in business
- Where and when will she access this mobile application
  - iPhone and mainly at nights before she watches the movie
- Motivation/Needs
  - She needs to find what she is looking for quickly
  - She needs to filter the movies according to their genre, title, yeear etc.
  - She needs to see whether they are available on Netflix or not
- Technology and access mechanisms that he regularly uses – desktop, mobile, operating system, browsers, et al
  - iPhone mostly, rarely iPad.
- Other
  - She also has Amazon Prima subscription but mainly watches the movies on Netflix.
  - She may use this service to find a good TV Show as well but not as often as searching for movies.

Product Backlog URL

Miro Backlog Board

Product Backlog Ordering Rationale

Minimum Viable Product first and then Technology Readiness.

Definition of Ready

Title
Expressed as User Story
Developers all understand what needs to be done
Dependencies are all understood and refined
No Impediments
Business value defined
Acceptante Criteria defined
Story Points Estimated

Whole-team relative-size estimating activity

Method used was T-Shirt-Sizes. This activity was only done by the developers.

Used points 10, 20, 30, 40, and 50 as the different size options.

Sprint 1

Note: All User Stories are expressed as user stories if you click into the details of a PBI. The titles of the PBIs are shorter on the backlog for brevities sake.
Forecasted Points: 100 Points Per Sprint
Rationale: There are 380 total points of User Stories planned in our backlog which are planned to complete throughout the bootcamp. There are four sprints so we divided by four and rounded up to an even 100. This will allow us to plan all of the user stories throughout the next four sprints.
Stories pulled into backlog: Our backlog is ordered in terms of what needs to get done first, we, the developers, pulled the maximum stories into our sprint from the top of the backlog that did not exceed our forecasted points.
All stories are less than half of our current forecast.
User stories were decomposed into tasks, in our Miro board, red items are tasks, and blue items are user stories as outlined by the key.
Kanban board link: Miro Board
Burndown chart: Also on the same Miro Board: Miro Board Miro doesnt keep the formatting of the burndown chart line so here are progressive screenshots of it
Daily Scrums: Scrums were completed in our slack channel when not able to meet on weekends due to time constraints of people. Here is a link directly to one days documentation of a scrum meeting: Sprint 1 Daily Scrum Chats
Impediment Removal Plan: Swarm the impediment as a team to come up with a solution or workaround to unblock the impediment.
Sprint board update and Burndown Updates: Screenshots of burndown updates are above. Screenshots of board below.
Pair programming evidence:
Working Software: Screenshot Proof:
Sprint Review: Decision made: Database creation task is required for the retrieval of the information using the email. It is not required for form page. Moving to next sprint PBI for revisiting quotation. Part 2 held on 11/15 with the stakeholder.
Sprint Retrospective Actions:
- Update User Stories to be more user story accurate
- Take out unused functionality
- Include unit tests in order to ensure robustness (This is in the backlog)
- Come up with definition of done (We completed this in the retro and moved it to completed because we thought it was important to do quickly.)