Professional Documents
Culture Documents
User driven -> But many users dont know what they want Micromanagement
You drive based on you knowledge -> you do your thing, I will do my thing,
we will patch at end. -> wrong, we need collaboration.
Narrative Collaboration:
o Keep the user in mind , whats value to the user, what will create a
valuable outcome and narrate the goals to the team keeping user in
mind
Do in small batches
o Will help to correct mistakes
o People in team should be allowed to come up with blue button
questions/alternatives and that should be taken based to
infrastructure team, analyzed and if need changes should be
brought it. It will help in creating not just an output for the client but
a valuable outcome for the client.
Manifesto of Agile:
We built software
Agile: Mitigate risk by building a product, by regularly interacting with the client
and building what they want
Product backlog:
Based on vision , whatever has to go into the product, those are entered
into product backlog
Sprint backlog:
A small manageable chuck from the product backlog is taken and put into
sprint backlog
Product owner
Scrum Master
Team
Daily scrum/daily meeting: update on project, any road blocks, a short meeting
for 15 mins
Scrum master: notes down all the blocks. Resolve the issues. So that the team
can work fast.
Product owner also participates in the meeting.
Senior master:
Burndown chart: to successfully self manage, gives the status of where and how
are we progressing for the goal.
Product review:
Meeting with the client of the actual working software based on the
functionalities in the sprint log.
Product review
Users gives feedback and product owner incorporates those in the product
catalog
Retrospective meeting:
Reference:
Lecture by Rajamanickam:
https://www.youtube.com/watch?v=gLd4NZLVrFw
1. Scrum
a. Each iteration -> sprint
b. More visibility to the customers
c. Business requirements are written as User stories
d. Contents of User Stories
i. Role that is going to be executed by the user stories
ii. Features addressed by user stories
iii. Benefits derived from user stories
e. User Stories are kept in backlog
i. Types
1. Product backlog
a. All user stories not just sprint user stories
2. Release/sprint backlog
a. Collection of many sprints
i. A release can contain two or more sprints
ii. A sprint may be very tiny, so we can work
and release multiple sprints together.
b. User stories should be prioritised and assigned
to sprint