How to Implement Agile & Scrum in your Startup

1.
How to ImplementAgile & Scrum in your Startup Kartik Poddar Nameer Khan

2.
What is Agile

3.
What is Scrum

4.
What will scrumdo for you? ● Scrum is a framework for developing and sustaining complex products ● Promotes Transparency and Openness ○ Vision Statement ○ Prioritized Product Backlog ○ Release Planning Schedule ○ Daily Stand ups / Review and retro Meetings ○ Burndown and Velocity Charts ● Scrum will help in raising all concerns, not solving them. Scrum is a tool, not a solution ● People will resolve concerns/problems

5.
What will scrumdo for you? ● Will make your developer team cross-functional ● Developers will be self organizing ● Developers decide how much can be done, instills ownership ● Sprint goals cannot change. Buffer can be present in a sprint ● Deﬁnition of done, will be speciﬁc to a team, decided by a team ● Every sprint we will inspect the Product and the Process

7.
Scrum Ideals ➔ Plan,Produce, Inspect and Adapt ➔ Daily Standups, Time boxed (15 mins) ➔ Retrospect before starting next sprint ➔ 1 Scrum Master, 1 Product Owner, 6-9 developers ➔ Discover and remove impediments ➔ Communicate ➔ Sprint Planning Meeting (team speciﬁc) 1 week -> 2 hours 2 weeks -> 4 hours

8.
Scrum Team ➔ ProductOwner Backlog, Priority, Roadmap, Expectations ➔ Developers Scoping, Implementing, Self Organizing, Task breakdown ➔ Scrum Master Leads change, Coaches, removes impediments, protects, servant leader

9.
Product Owner

10.
Developer Team ● Self organizing ○Swapping tickets among peers ○ Ticket break down ○ Making sure the team sprint is complete ● Cross functional ○ As a team they can achieve any of the product goals ○ QA, Devs, UI/UX can all interchange tasks if they deem it necessary ○ Recommended team size 6+/-3 ● Team splitting if required ○ For larger teams, multiple teams work in parallel Get dev’s to sit next to each other Developers are -> FE, BE, QA, Automated QA, UI/UX A team of 2 FE, 2 BE A team of 4 Full Stacks (which is cross functional ?)

11.
Scrum Master

12.
Scrum Master

13.
Let’s see atypical Project tasks distributed across a Scrum Team

14.
Project Tasks Facilitates discussions Determinesrequirements Determines how much is realistic in 1-4 weeks Removes impediments Vision and Goal / Product Assigns tasks to team Day to day task tracking Coaches team to improve Project Schedule management Leading a change to increase success Tradeoff between Scope, schedule, cost, quality Budget and Stuff Scrum Master Product Owner Developers

15.
Project Tasks Facilitates discussions Determinesrequirements Determines how much is realistic in 1-4 weeks Removes impediments Vision and Goal / Product Assigns tasks to team Day to day task tracking Coaches team to improve Project Schedule management Leads change to increase success Tradeoff between Scope, schedule, cost, quality Budget and Stuff Scrum Master Product Owner Developers

16.
Project Tasks Facilitates discussions Determinesrequirements of a product/project Determines how much is realistic in 1-4 weeks Removes impediments Vision and Goal / Product Assigns tasks to team Day to day task tracking Coaches team to improve Project Schedule management Leads change to increase success Tradeoff between Scope, schedule, cost, quality Budget and Stuff Scrum Master Product Owner Developers

17.

18.

19.

20.

21.

22.

23.

24.

25.

26.

27.
SCRUM QUOTES

28.
Let’s do an experimentfor one Sprint

29.
The truest measure ofprogress is how much working software you have

30.
If you wantto improve, you have to change.

31.
If you say“yes” to something, you make it more likely to happen again

32.
Pretending everything’s OK just allowsthe problems to get worse

33.
Team Activity. ● Teamsof 4-5 ● Get Blank sheets - At-least 50 ● Get a ruler to help in dividing sheets ● Get expected vs actual sheet ● After team activity, please return the expected vs actual sheet ● Please do pick up fallen paper, and help in cleaning Tip Sit with diﬀerent team members. Ideally people you have never worked with

34.
What is theActivity 1. Need to make paper airplanes 2. The paper airplane should hit the wall, only then is it counted as a success. 3. Plan -1min 4. Produce -3mins 5. Retrospect -1min 6. Respect each other What are the Rules 1. Respect time boxes 2. Be honest 3. One fold per person 4. Someone will have to throw the paper plane, and it should reach the wall 5. Take care of the expected vs actual sheet

35.
5 Questions, after3 rounds ● What if testing airplanes only keeps happening at the end? ● Did u know in advance what the best way to work as a team was? ● Can the team next to you, work the way your team works ● Who was responsible for deciding what each member should be doing in the sprint ● Who was responsible for hitting the goal?

36.
Team Activity -Round 4 Management Pressure Tip Sit with diﬀerent team members. Ideally people you have never worked with

37.
Team Activity -Round 5 Let’s Remove Blockers Tip Sit with diﬀerent team members. Ideally people you have never worked with

38.
Videos and Links ●A working day for a scrum master (must watch): https://vimeo.com/223279476 ● Scrum at scale ○ Less: https://less.works/ ○ Scrum@scale: https://www.scrumatscale.com/scrum-at-scale-guide/ ○ Safe: https://www.scaledagileframework.com/ ○ Nexus: https://www.scrum.org/resources/scaling-scrum

How to Implement Agile & Scrum in your Startup

More Related Content

What's hot

Similar to How to Implement Agile & Scrum in your Startup

Recently uploaded

How to Implement Agile & Scrum in your Startup