SCRUM & KANBAN
They are both Agile development environment.
SCRUM (Most popular)
- Sprint planning meeting
Take the most important features from the top of your backlog and move it to the sprint backlog
You talk about what needs to be done to implement it.
- The start of the development process
A sprint takes 2 weeks.
Your team works on the tickets by taking them to “In progress” and then “Done”
At the end of the 2 weeks, you should have completed everything in the sprint backlog; if not, they go into the next sprint.
Use tickets to track progress (Sprint backlog >> WIP >> Done)
- Standup meetings (Daily meetings, tasks, and assignments)
Daily meetings are held in the morning.
People remain standing during the meeting, for it to remain brief and concise.
Every team member makes a summary of their work.
- Retrospective meeting (meeting after sprint)
You meet with your team at the end of each sprint
You talk about 3 main things; the last sprint, what went well and what didn’t
- Daily meetings, flexibility, testing, customer feedback
KANBAN (Kahn-Bahn) Lecture 25
Kanban is not as strict as Scrum in terms of meetings and times. It uses boards which have columns with cards that can move from one column to another, to reflect the state of the item; “To do”, :In progress” or “Done”. The number of items in each state is up to you or your team to decide.
- More relaxed way but it makes it more difficult to estimate how much time it is going to take to develop items.
- It does not use sprint
- Difficult to know the estimated time of completion
Waterfall Development (Lecture 26)
This is the opposite of Agile. All features of a product are developed at the same time. It is riskier. It is much harder to adapt to the market feedback after you’ve already built everything.
- Develop and roll out all the features
- Users may not want the ones you fully developed
Example of Agile – Creating music playlist in a music app
Everyone on the team gets together and decides core features.
Developers create the database; product managers create wireframe.
Implementing basic features
Everyone is in close communication and collaboration.
Example of Waterfall – Creating an OS, Engine control systems in cars, and Building skyscrapers.
Share with your friends: |
