1
00:00:00,717 --> 00:00:03,783
In Agile a team basically has three main roles

2
00:00:04,217 --> 00:00:08,250
The product owner, the scrum master and the delivery team

3
00:00:08,717 --> 00:00:11,450
And most people fall within the delivery team

4
00:00:12,383 --> 00:00:14,450
The product owner is the end customer

5
00:00:14,650 --> 00:00:16,817
Or a person who represents the end customer

6
00:00:17,550 --> 00:00:20,683
And their main role in the Agile project is define priorities

7
00:00:21,017 --> 00:00:25,950
and provide input to the project team on what the team shows them in demo sessions.

8
00:00:26,583 --> 00:00:28,883
The scrum master is the Agile sensei

9
00:00:29,350 --> 00:00:31,383
Think about him as a team leader

10
00:00:31,950 --> 00:00:34,617
And that can be a Project Manager, a lead Developer

11
00:00:35,283 --> 00:00:38,317
a person who actually and formally has the role of scrum master

12
00:00:38,950 --> 00:00:42,783
or pretty much anyone who wants to play this role and has Agile knowledge

13
00:00:43,450 --> 00:00:47,717
Ultimately, the main thing is that the team agrees on who the scrum master is

14
00:00:48,050 --> 00:00:51,483
And of course they can also rotate the role if they feel like doing it

15
00:00:52,150 --> 00:00:55,417
As all of you know I work with Agile projects every day

16
00:00:55,883 --> 00:01:00,883
In some, I'm the scrum master. But in the sum, the scrum master is actually a developer

17
00:01:01,750 --> 00:01:05,083
In others a tester and in others even an architect

18
00:01:05,550 --> 00:01:07,683
Like I said, anyone can play this role

19
00:01:08,217 --> 00:01:12,117
As long as they understand the responsibilities and have sufficient Agile knowledge

20
00:01:12,650 --> 00:01:16,750
If someone hasn't even gone through Agile training or finished this course at a minimum

21
00:01:17,283 --> 00:01:20,150
Then I wouldn't recommend that person to play the role of scrum master

22
00:01:20,617 --> 00:01:23,550
Since he or she probably wouldn't do it properly

23
00:01:24,383 --> 00:01:26,117
And finally, the delivery team

24
00:01:26,917 --> 00:01:31,717
Well that's pretty much everyone else so developers, testers, business analysts etc

25
00:01:32,383 --> 00:01:35,950
The main responsibility of the delivery team is quite simple: to deliver!

26
00:01:36,650 --> 00:01:40,550
They are in charge of getting the work done and are key to the team's success.

27
00:01:41,317 --> 00:01:43,783
Now, let's talk about the tools used in Agile

28
00:01:44,250 --> 00:01:46,350
And don't worry if you feel you need more information

29
00:01:46,650 --> 00:01:51,650
I'll add several links to all of these tools so you can go over them and read about them in more detail

30
00:01:52,050 --> 00:01:54,917
The first tool I want us to review is the burn down chart

31
00:01:55,383 --> 00:02:00,383
As its name implies a burn down chart is a chart that shows the burn down of work

32
00:02:01,083 --> 00:02:03,317
So basically you see the number of story points

33
00:02:03,583 --> 00:02:06,617
The team is delivering over time, so your team's velocity

34
00:02:07,317 --> 00:02:12,317
On the X axis you have your sprints and on your Y axis, your story points

35
00:02:13,083 --> 00:02:15,183
as you can see in the graph on your screen

36
00:02:15,583 --> 00:02:20,583
You can do this manually in Excel or use tools that automatically do this for you such as JIRA

37
00:02:21,783 --> 00:02:23,983
The great thing about the burn down chart

38
00:02:24,217 --> 00:02:27,950
Is that in it you can see several things about your project and your delivery

39
00:02:28,650 --> 00:02:31,183
For example, you can see the total amount of work

40
00:02:31,717 --> 00:02:35,317
The amount of work remaining and even your team's velocity

41
00:02:36,117 --> 00:02:40,350
The Kanban Agile board is probably one of the most exciting things about Agile

42
00:02:40,817 --> 00:02:43,917
And I say exciting because of its simplicity and value

43
00:02:44,283 --> 00:02:49,217
an Agile Kanban board is a visual representation of the work the team is doing in a sprint

44
00:02:49,550 --> 00:02:51,350
You basically have three or four columns

45
00:02:52,350 --> 00:02:56,483
And your user stories displayed in those columns to reflect the state of those user stories

46
00:02:56,950 --> 00:02:59,483
Generally, you would have a column with the heading To Do

47
00:03:00,050 --> 00:03:02,617
Another one with the heading In Progress

48
00:03:03,183 --> 00:03:07,950
Another one with the heading In QA and a final one with Done

49
00:03:08,417 --> 00:03:12,083
Most Agile teams use a physical Agile Kanban board and sticky notes

50
00:03:12,450 --> 00:03:14,483
As per the picture you see on your screen

51
00:03:15,050 --> 00:03:17,910
But a lot of teams also use digital boards

52
00:03:18,350 --> 00:03:21,983
There is no right or wrong answer on whether using paper or digital

53
00:03:22,550 --> 00:03:24,917
Use whatever works best for you and your team

54
00:03:25,283 --> 00:03:29,450
Personally, I prefer digital boards and generally use Trello or JIRA

55
00:03:30,117 --> 00:03:32,950
But if a team prefers paper I'm happy to do it

56
00:03:33,250 --> 00:03:36,450
and have no issues with using a physical Agile Kanban board

57
00:03:36,950 --> 00:03:39,183
I'll add links under the resources for this lecture

58
00:03:39,450 --> 00:03:42,650
to the tools I just mentioned and to the examples of this concept