This document discusses project management methodologies Scrum and Kanban. It describes Scrum as an agile framework that involves breaking work into tasks in a backlog, conducting sprints to complete tasks within a deadline, and daily stand-ups. Kanban involves visually tracking work on a board as tasks move from open to pending to in progress and completed. The document suggests applying these methods by having students self-organize projects by breaking work into tasks and sprints with commitments while the professor participates.

1. PROJECT MANAGEMENT METHODOLOGIES
SCRUM + KANBAN
Presenter: Cassiano Campes
Computer Systems Laboratory
Suwon - 29th
Jan. 2018

2. WHAT IS SCRUM?
● Is an agile way to manage a project, usually software development
● Scrum is often perceived as a methodology
● Rather than a methodology:
○ Think of it as a framework for managing a process
2

3. BASIC CONCEPTS: THE PROBLEM
● Define the product (target) you are trying to develop and deliver
○ Example: An Operating System for a new 96-bits RISC architecture
■ Preemptible scheduler
■ Kernel must be developed in modules
■ Support to dual-core CPUs
■ ...
3

4. BASIC CONCEPTS: THE DEADLINE
● Define the hard deadline even if it is not required
○ This deadline is where you deliver the product to the customer
○ At this point the work must be done!
○ Done != almost done
4

5. BASIC CONCEPTS: THE TASKS
● Break the problem into small deliverable tasks
○ These tasks must be achievable in a deadline time manner
○ A completed task must provide value to the final problem
○ Example: Non-preemptible scheduler
i. Simple Round-Robin Scheduler
ii. Shortest-Job-First Scheduler
iii. Preemptible Scheduler
5
Tasks are incremental

6. BASIC CONCEPTS: THE BACKLOG
● Once the tasks are defined, they remains in the backlog
6
The big
problem

7. BASIC CONCEPTS: THE BACKLOG
● Once the tasks are defined, they remains in the backlog
7
The big
problem
The scheduler Kernel modules Dual-core support
Backlog

8. BASIC CONCEPTS: THE SPRINT
● A Sprint consists of a time-window where in the end:
○ Selected tasks for this Sprint are delivered
● Sprint “size” must be defined: i.e.: 1 or 2 weeks
8

9. BASIC CONCEPTS: THE SPRINT
● A Sprint consists of a time-window where in the end:
○ Selected tasks for this Sprint are delivered
● Sprint “size” must be defined: i.e.: 1 or 2 weeks
9
The scheduler Kernel modules Dual-core support
Backlog
SPRINT #1 2-weeks

10. BASIC CONCEPTS: THE SPRINT
● A Sprint consists of a time-window where in the end:
○ Selected tasks for this Sprint are delivered
● Sprint “size” must be defined: i.e.: 1 or 2 weeks
10
The scheduler Kernel modules Dual-core support
Backlog
SPRINT #1 2-weeks

11. BASIC CONCEPTS: THE SPRINT
● A Sprint consists of a time-window where in the end:
○ Selected tasks for this Sprint are delivered
● Sprint “size” must be defined: i.e.: 1 or 2 weeks
11
The scheduler Kernel modules Dual-core support
Backlog
SPRINT #1 2-weeks

12. BASIC CONCEPTS: THE ITERATION
● After finishing a Sprint, evaluate the delivered tasks
● As the development evolves, better understanding is constructed
● Refinements can be applied:
○ Previous tasks in backlog are evaluated
○ Create or remove tasks as needed
● Think as “constructing into small steps”
12

13. BASIC CONCEPTS: THE STAND-UP
● Daily “report” answering three basic questions:
i. What I am doing?
ii. What I will do next?
iii. Do I have any problem?
● Stand-up reduces the time to take actions
13
SPRINT #1 2-weeks
2-weeks delay

14. BASIC CONCEPTS: THE STAND-UP
● Daily “report” answering three basic questions:
i. What I am doing?
ii. What I will do next?
iii. Do I have any problem?
● Stand-up reduces the time to take actions
14
SPRINT #1 2-weeks
2-weeks delay
Day 1 Day 2 Day 3 Day N
1-day delay
Stand-up

15. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
15

16. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
16

17. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
17

18. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
18

19. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
19

20. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
20

21. BASIC CONCEPTS: OVERALL VIEW
● Backlog, Sprint, Iteration, Stand-up, ...
21

22. HOW USE SCRUM IN OUR RESEARCH?
● SCRUM relies on self-organized teams
● Sprints are organized with commitment to finish the tasks
● Each student manages its own project
○ Break it into tasks, prioritize tasks, organize sprints, commit to deadlines, …
● Professor participates following the projects
22

23. SCRUM
HOW TO APPLY?
23

24. WHAT IS KANBAN?
● Track what is being developed with specific tools
24
Project X
Sprint 1
Sprint 2
Sprint 3
Task 1
Task 2
Task 3
Task 1
Task 2
Task 3

25. HOW CAN IT BE USED?
25
Project X
OPEN
Task 1 Task 2
Task 3
Task 4Task 5
Task 6
PENDING IN PROGRESS COMPLETED

26. HOW CAN IT BE USED?
26
Project X
OPEN
Task 1 Task 2
Task 3
Task 4Task 5
Task 6
PENDING IN PROGRESS COMPLETED
Use colors

27. HOW CAN IT BE USED?
27
Project X
OPEN
Task 1 Task 2
Task 3
Task 4Task 5
Task 6
PENDING IN PROGRESS COMPLETED
Task 4
This task consists
of bla bla bla, and
bla bla bla...

28. HOW CAN IT BE USED?
28
Project X
OPEN
Task 1 Task 2
Task 3
Task 4Task 5
Task 6
PENDING IN PROGRESS COMPLETED
Task 4
This task consists
of bla bla bla, and
bla bla bla...
A developer can work
only in one task at time

29. WHAT TOOL TO USE? ● https://app.clickup.com
29

30. Q&A
THANK YOU!
30