scrum and testing

Scrum and testing

This is not the way I see it Let me show SCRUM through my

eyes..

We are going to try something called

SCRUM

That means no more planning and no

more documentation. Just start writing code.

There is almost no testing effort

WTF!?!

Claudiu Draghia www.brainforIT.com

Why Not Waterfall??“Managing the development of large software system” by Winston W. Royce, page 2:

I believe in this concept but the implementation described is risky and invites failure.

………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………

However I believe the illustrated approach to be fundamentally sound. The remaining of this discussion presents 5 additional features that must be added to this basic approach to eliminate most of the development risks.

Ant it goes on for 9 more

pages...

Waterfall is sound and solid development process if applied as it is not based on a feelingThe same thing is true for SCRUM...…

What will we do• We will go through the “word”• Take the Wikipedia definition of SCRUM and go through each aspect

– What is a software and what is a product?– What are the agile values and principles?– What is iterative and incremental?

• Go through the SCRUM ‘s father guideline• Challenge SCRUM and SCRUM adoption• Take a user story and SCRUM it

If you are new to SCRUM there quite some strange terms and concepts If something does not make sense just shout my name, I’ll stop and answer your question or reiterate what it means.

The scrumFollowing some infringements of the rules play

is restarted with a scrum.Eight players from each team bind together in their own 3-4-1 formation in a

crouching position.The two formations engage each other head-on to form a single mass off 16

players.The ball is then put into the tunnel between the opposing formations and each

team attempts to get control of the ball with their feet.Find out more about the scrum in the pages about how to play rugby.

What is scrumThe word

What is scrumThe word

Team and groupindividual accountability

share information and perspectives

individual goals

concern with one's own outcome and challenges

purpose, goals, approach to work shaped by manager

discussion, decision making, problem solving, and planning

Individual and mutual accountability==team goals =concern with outcomes of everyone and challenges the team faces=purpose, goals, approach to work shaped by team leader with team members=

teams' failure=individual failureUsually the surgery is a success but the patient

dies

How is the surgery?

The customer does not care if you have done the best tests if the application is not working

on production

What is scrum

• Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development

for managing software projects and product or application development

Your focus is not only the software application

but also the product with all its attributes

It has to be clear to anyone what is “The Product” How you define the product is up to you.

This is the starting point for everything.

What is scrum

• Scrum is an iterative and incremental agile software development framework

We are uncovering better ways of developing software by doing it and helping others do it.

Individuals and interactions over processes and tools

February 2001, 17 software developers met to discuss lightweight development methods. They published the Manifesto for Agile Software Development. It gives us a set of values and principles.

Through this work we have come to value:

This does not mean we do not need processes. They have to

exists and they have to be easily changed and adaptive

No matter what you will always put in your

time sheet.

http://www.agilemanifesto.org/

What is scrum




Working software over comprehensive documentation


This does not mean no

documentation. People do not come at the beginning of a project and leave

at the end.

Business flows are extremely important

in understanding changes.

What is scrum




Customer collaboration over contract negotiation


How should the customer see this?

Who can explain him this and get his

agreement?

Contracts have to exists. They way they are made has to be

changed

What is scrum




Responding to change over following a plan.


The plan has to be simple so that we can

change it quickly.

Change without any understanding leads to chaos. Changes need to be understood before

done.

What is scrum


We follow these principles:


Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

The whole focus is on the customer

We deliver all the time. We do not have the time to test everything

Customer has to have clear

expectations and these should be

known to everyone

What is scrum




Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Changing requirements has to be controlled.

Uncontrolled changes lead to chaos.

What is scrum




Deliver working software frequently, from a couple of weeks to a couple of Months, with a preference to the shorter timescale.

What does working software mean for you?

Functionality

Security

Performance

Customer support

Deployment

What about the customer?

What is scrum




Business people and developers must work together daily throughout the project.

Business should know about development,Development should know about business

What is scrum




Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job…….

This one is for the management and

HR.

Before asking for results give us the

means.

DO

NE

Trust means to give the chance to fail. Failing is always a option…don’t be afraid…

What is scrum




The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

The telephone has been in usage since 1950... Give us more... It’s the 21st century

What is scrum




Working software is the primary measure of progress.

Working software has to

be definedIf this is the measure

then this has to be known and accepted by

everyone

You have to prove that you respected the

definition

What is scrum




Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

It’s ok to be exited or nervous for a

delivery

This requires discipline and self

determination

What is scrum




Continuous attention to technical excellence and good design enhances agility.

Lessons learned

Best practices Testing approach and methodology

Trainings

What is scrum




Simplicity--the art of maximizing the amount of work not done--is essential. ?

Among other things, it means that a team can spend an amazing amount of time building a complex system that will handle all possible eventualities - or it can do only what is needed right now, get it right, and get it out the door.

What is scrum




The best architectures, requirements, and designs emerge from self-organizing teams.

Self-organization = is a process where some form of global order or coordination arises out of the localinteractions between the components of an initially disordered system

Leader must arise from the

interactions

It is not a democracy but

more a meritocracy

What is scrum


At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.



In SCRUM this is done at the end of every

sprint.

You will have to find ways of improving

What is scrum


Agile does not refer only to the development team but everyone

involved in the product development . It is not a change

in a “single place”.

What is scrum

• Scrum is an iterative and incremental?

“Iterating” builds a rough version, validates it, then slowly builds up quality

A more iterative allows you to move from vague idea to realization making course corrections as you go.

1 2 3 4 5

Let’s start…..

Iterative digging tools

Prod

uctio

n

Iterative development

Develop Test Develop Test Develop Test

Develop Test

Waterfall

Iterative

Development and QC work side by side delivering increments through iterations

Testing is no longer a gateway for production Definition

of done

Feedback about how the

software is behaving faster

Regression results have to be “fast”

If this is different in waterfall and iterative then SCRUM has made visible the mismatch between dev and testing that already existed

If bugs are not fixed quickly iterations will

be slow

What is scrum

• Scrum is an iterative and incremental?

“Incrementing” builds a bit at a time Jeff Patton www.AgileProductDesign.com

1

Incrementing calls for a fully formed idea.

And, doing it on time requires dead accurate estimation.

2 3 4 5

Let’s see….

Incremental software development methods have been traced back to 1957.

Incremental development

Instead of having a final working product

We have “something working” at each milestone

Each increment has to be functional and usable. It

has to bring business value. It can be $$$$

tomorrow

How do you eat a elephant?


==

They are part of a epic

Testing has to validate if the “whole” is working

not only the current user story.


“Incrementing” and “Iterating”SCRUM combines both iterative and incremental

1 2

Let’s watch a SCRUM Mona Lisa

Start a new sprint and carry on

What is scrum• Scrum is an iterative and incremental

Incrementing calls for a

fully formed idea.

“Iterating” builds a rough version, validates it, then slowly builds up

quality

“Incrementing” builds a bit

at a time

Since this is a principle you have to apply it to how

you develop software also

You create smaller bits

that in the end have to fit

with the whole

Increment applies not only to the

“end sprint product” but also

how you build

What is scrum• In 1995, Jeff Sutherland and Ken Schwaber jointly presented a paper describing the

Scrum methodology, its first public presentation

• In 2001, Schwaber worked with Mike Beedle to describe the method in the book Agile Software Development with Scrum

• Now he has a website

What is scrumSchwaber’s SCRUM guide

Sprint Planning

Daily SCRUMReview

Retrospective

The Scrum Team

The Product Owner

The Development Team The Scrum Master

Scrum Events

The Sprint

Scrum Artifacts

Product Backlog

Sprint Backlog

Schwaber’s SCRUM guideThe Development Team = THE PIGS

Others (not involved in development) = THE CHICKENS

The person who says it cannot be done should not interrupt the person doing it.

Chinese Proverb

Schwaber’s SCRUM guideSprint Planning

What?

Product backlog

Product owner

Development team

SCRUM Master

Time boxed to 8 hours for a one month sprint

What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved?

apabilitiesonditionsonstrains

3CCCC

These are the acceptance

criteria

They are just a part of the

definition of done

Who verifies and validates

these?

To validate them you need

test case

Acceptance criteria need to

be clear and testable


What?

Product backlog

Product owner

Development team

SCRUM Master




3CCCC

The whole purpose of this meeting is for the development team to

have a clear understanding about

what it required

You have to use any means

necessary. SCRUM tells you what to do not how to do

it.


What?

Product backlog

Product owner

Development team

SCRUM Master




3CCCC

IN SCRUM THIS CAN AHAPPEN ALSO


What?

Product backlog

Product owner

Development team

SCRUM Master




3CCCC


What?

Product backlog

Product owner

Development team

SCRUM Master


Story Points



3CCCC

Planning poker

Fibonacci numbers

Story points represent

complexity and duration. The scale is:

1, 2, 3, 5, 8, 13, 21….

You have to take into account that you have to build iterative and the final product has

to be a increment.

The burn down chart


What?

How?Product backlog

Product owner

Development team

SCRUM Master


Story Points


Define activities


3CCCC

Planning poker

Fibonacci numbers


What?

How?Product backlog

Product owner

Development team

SCRUM Master


Story Points


Define activities


3CCCC

Planning poker

Fibonacci numbers

You have only 4 hours to drive the direction for the next

weeks.YOU have to prepare.

Everything related to testing has to be as clear as possible.


What?

How?Product backlog

Product owner

Development team

SCRUM Master


Story Points


Define activities


3CCCC

Planning poker

Fibonacci numbers

You have to :•Make a impact analyses•Spot out any dependencies•Evaluate how you can fulfill the definition of done. •Define your activities at least for the next couple of days•You need to have everyone on your side


What?

How?Product backlog

Product owner

Development team

SCRUM Master

Sprint Goal


Story Points


Define activities


3CCCC

Planning poker

Fibonacci numbers

Daily SCRUM Routine

We follow some basic rules

If the PO wants something new in

the sprint he has to remove something

of similar value

We pick up task voluntarily

It has to be in the best interest of the

team (priority& commitment)

We never start something that

cannot be finished in the current sprint

To do this we have secondary skills to

help the team closing the current activities

We attend a SCRUM meeting every day

Beside the SCRUM we meet whenever it

is necessaryTesting has to

become a secondary skill for

everyone

Test case, approach and scripts have to be understood by

everyone in the team

Schwaber’s SCRUM guide

Daily SCRUM

Development teamSCRUM Master

Time boxed to 15 minutes every date

What did I do yesterday that helped the Development Team meet the Sprint Goal?What will I do today to help the Development Team meet the Sprint Goal?Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Require more information

Sprint Goal


Review

Sprint Goal

Development team

SCRUM Master

Only DONE items

The definition of DONE has to be

respected. Only DONE items should be

presented

Who validates if the definition of done is

respected?

If one fails everyone fails


Development team

SCRUM Master

Retrospective

What went well?What can be improved?

Create a plan for implementing improvements to the way the Scrum Team does its work.

Adopt SCRUM?Step Question Answer

1 Do you want to be a PIG? Yes No

2 Are you sure you value autonomy and responsibility? Yes No

3 Do your colleagues value autonomy and responsibility? Yes No

4 Does management want to you to be a PIG? Yes No

5 Will they actually support you and follow SCRUM? Yes No

If you have just one No answer...then you cannot do it…

Maria Montessori(1870 -1952)

I devised a education approach characterized by an emphasis on independence, freedom

within limits, and respect for a child’s natural psychological,

physical, and social development.

Montessori Education vs SCRUM

Mixed age classrooms, with classrooms for children aged 2½ or 3 to 6 years old by far the most common = Cross-Functional Teams

Student choice of activity from within a prescribed range of options = Tasks Pickup by voluntary method

Uninterrupted blocks of work time = Sprints

Specialized educational materials developed by Montessori and her collaborators

Poker Planning, estimation techniques, Sprint and Release

Planning=

Larry page Sergey Brin

Dan Pink’s

SCRUM gives you

autonomy and it gives you

a purpose every sprint

If you do not want to be a

master you will not

succeed in SCRUM

In 1971, working for IBM I noticed cultural differences between

countries and defined a set of indexes

ROMANIA

Loyalty in a collectivist culture is paramount, and over-rides most

other societal rules and regulations

Geert Hofstede’s researchPeople accept a hierarchical order

in which everybody has a place and which needs no further

justification.

Romania scores 90 on this dimension and thus

has a very high preference for avoiding

uncertainty

Let’s take a user story

As a user I want to be able to generate a report with my auctions in order to have a clear overview about my activities and the money I have to cash in.

Recap- everything related to testing

• Your focus is not only the software application but also the product with all its attributes (slide7)

• We deliver all the time. We do not have the time to test everything (slide 12)• What is working software for you: Functionality, Security, Performance, Customer support,

Deployment (slide 14)• Working software has to be defined. If this is the measure then this has to be known and

accepted by everyone (slide 18)• You have to maintain a constant pace: This requires discipline and self determination (slide

19)• You have to aim for technical excellence (Lessons learned, Best practices, Testing approach

and methodology, Trainings (slide 20)• You will have to find ways of improving (slide 23)• Development and QC work side by side delivering increments

through iterations (slide 28)• Testing is no longer a gateway for production (slide 28)• Regression results have to be “fast” (slide 28)

• If bugs are not fixed quickly iterations will be slow (slide 28)• Testing has to validate if the “whole” is working not only the current user story. (slide 23)• Acceptance criteria need to be clear and testable (slide 39)• Everything related to testing has to be as clear as possible. (slide 46 in regards to the 2nd half

of the planning meeting)• Test case, approach and scripts have to be understood by everyone in the team (slide 49)• Testing has to become a secondary skill for everyone (slide 49)

Recap- everything related to testing

Credits and inspiration• Wikipedia• http://bibleopia.wordpress.com• https://www.boundless.com/management/groups-teams-and-teamwork/defining-teams-and-teamwork/d

ifferences-between-groups-and-teams/• http://www.dummies.com/how-to/content/differences-between-work-groups-and-teams.html• http://geert-hofstede.com/countries.html• http://www.ted.com/talks/dan_pink_on_motivation.html• http://www.deborahschultz.com/deblog/2007/05/technology_chan.html• http://gapingvoid.com/2007/06/17/but-what-if-i-fail/• http://www.testertroubles.com/2009/04/scrum-pigs-and-chickens.html• http://www.cavdar.net/2011/10/10/characteristics-of-a-good-software-requirements-specification-srs/• https://www.scrum.org/• http://www.agileproductdesign.com/blog/dont_know_what_i_want.html• http://testobsessed.com/wp-content/uploads/2011/04/AgileTestingOverview.pdf• http://snarap.wordpress.com/2011/09/14/mmscrum/• http://www.dilbert.com/• http://www.implementingscrum.com/section/blog/cartoons/• http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf

http://bibleopia.wordpress.com/

https://www.boundless.com/management/groups-teams-and-teamwork/defining-teams-and-teamwork/differences-between-groups-and-teams/

https://www.boundless.com/management/groups-teams-and-teamwork/defining-teams-and-teamwork/differences-between-groups-and-teams/

http://www.dummies.com/how-to/content/differences-between-work-groups-and-teams.html

http://geert-hofstede.com/countries.html

http://www.ted.com/talks/dan_pink_on_motivation.html

http://www.deborahschultz.com/deblog/2007/05/technology_chan.html

http://gapingvoid.com/2007/06/17/but-what-if-i-fail/

http://www.testertroubles.com/2009/04/scrum-pigs-and-chickens.html

http://www.cavdar.net/2011/10/10/characteristics-of-a-good-software-requirements-specification-srs/

https://www.scrum.org/

http://www.agileproductdesign.com/blog/dont_know_what_i_want.html

http://testobsessed.com/wp-content/uploads/2011/04/AgileTestingOverview.pdf

http://testobsessed.com/wp-content/uploads/2011/04/AgileTestingOverview.pdf

http://snarap.wordpress.com/2011/09/14/mmscrum/

http://snarap.wordpress.com/2011/09/14/mmscrum/

http://www.dilbert.com/

http://www.dilbert.com/

http://www.implementingscrum.com/section/blog/cartoons/

http://www.implementingscrum.com/section/blog/cartoons/

http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf

http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf

scrum and testing

Documents