Scrum and Agile Values

Agile and Scrum Values

Presented by Kamal Tejnani,Agile Coach, Agile CoE

08/24/2015

2

Scrum Values

Because we focus on only a few things at a time, we work well together and produce excellent work. We deliver valuable items sooner.

WIP as described specifically in Kanban

What happens in our projects ?

3

Focus

As we work together, we express how we're doing, what's in our way, and our concerns so they can be addressed.Transparency, willingness to listen, communicate openly, Fail-Fast …Why be open in the Standups especially wrt the Impediments and Blockers – highlight risks earlier rather than later

4

Openness

As we work together, sharing successes and failures, we come to respect each other and to help each other become worthy of respect

Needed in all projects, but Scrum Projects cannot succeed without this - can we work and deliver together over long periods of time, from one Release to another without respecting one another - THINK

5

Respect

Scrum Master as Servant Leader

Because we work as a team, we feel supported and have more resources at our disposal. This gives us the courage to undertake greater challenges

Courage to be honest, courage to stand up to lack of respect, courage to tell the PO that we are not getting the stories 2 days in advance, courage to tell the PO that DoR is not being met, Courage to tell the SM that we are not getting adequate support from him in unblocking impediments ….

6

Courage

• We commit to the team. • Commit to meet our Sprint Goals• Commit to meeting the DoD• Commit to delivering best with the least number of defects• The success of the Release depends upon the team’s capability to meet its Sprint Commitments every time.

7

Commitment

Agile Manifesto

9

Principles on which the Agile Manifesto is based

• What does this mean ?

• Processes and Tools – Bureaucracy (red tapism ?)– Approvals, hand-offs, sign-offs– Formal notes– Email trails– Not in my jurisdiction (Indian Police always does that) and refer to policies

• As software developers, we are actually passionate about tools. And we love our processes as well. Both processes and tools help us get things done

• How many processes can you put in place, given the kind of projects that are implemented in Agile

• But will this work in a Distributed Model between Onsite and Offshore

• Will it work for us ?

10

Individuals and Interactions over Processes and Tools

Stacey Matrix

11

Working software over comprehensive Documentation

• Agile processes harness change for the customer's competitive advantage

• What does this mean ?

• Arbitrary changes within the Sprint ?

• Changes during Grooming Before Estimation After Estimation Before Planning After Planning Before Sprint has started After Sprint has started

12

Welcome changing Requirements even late in Development

13

Business people and developers must work together daily throughout the project

• Why ?

• During Release Planning

• During Grooming

• Even during Estimation to get clarifications if needed

• During the Sprint

• Demos

• Risks highlighted during Standups

Give them the environment and support they need and trust them to get the job done

• Stacey Matrix again – the kind of projects that are implemented in Agile

• Empowered teams deliver better

• Self-organized teams support one another

• Teams trust one another

14

Build projects around motivated individuals

• Less Technical Debt

• Easier to make changes

• Your code changes will not have negative impacts

• You will be able to deliver faster, with good quality thus making you Agile

15

Continuous attention to technical excellence and good design enhances agility

Anything I missed out ?