A personal journal on the day to day implementation of scrum at my restaurant in London – By Riccardo Mariti – (Note: In case your wondering why I'm using a basic Wordpress site, I figured that it would load and optimize better on multiple devices so will be easier for you to read!)
The essence of Scrum is coming up with an MVP (minimum
viable product). The smallest possible version of something that you can put
into somebody’s hands to get feedback as soon as possible. In shortening this “feedback
loop”, we are able to find out super-quickly what works and what does not. The
above article shows that even experts, seasoned, experienced, entrepreneurs
have no idea what will work and what will not. The “secret” is not to try and
guess, but to run a simple experiment; put something in the physical universe
and see if it works.
This post was taken directly from the Scrum Alliance Website to see the original, click here
Scrum Values
In 2001, a group of 17 independent software development thinkers gathered in the mountains of Utah to talk about Agile methodologies. They worked to create a set of compatible values based on trust and respect for each other, and to promote organizational models centered on people, collaboration, and building communities in which they – and others – would want to work.
After much skiing, talking, relaxing, and eating, they arrived at four common values that led to the development of the Agile Manifesto, with the core values being:
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan Using these as a guidepost, additional Scrum values have been created, and continue to be developed and modified (in true Agile fashion). These five values are the foundation for a Scrum team’s processes and interactions:
Focus
Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
Courage
Scrum Team members have courage to do the right thing and work on tough problems.
Openness
The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
Commitment
People personally commit to achieving the goals of the Scrum Team.
Respect
Scrum Team members respect each other to be capable, independent people.
Notes taken from “Nokia Test: Where did it come from?”[1] (ScrumInc –
Jeff Sutherland )
Full Transcript – Jeff Sutherland speaking for 6 minutes
(watch video)
Everyone wants to know “How well are we doing and how do we
get better?”
The teams want to know that, the leadership wants to know
that, the management wants to know that. So, over the years we’ve developed a
short test of a few simple questions that can give us a fix on “how well is
this team doing?” It started at Nokia in Finland and so has come to be known as
the “Nokia Test”.