Interesting facts, I learned today from Amazing Amazon Story

Interesting facts, I learned today from Amazing Amazon story: from Jeff Bezos speech.

For Entrepreneurs,The Role of the Risk in Life: Risk is the necessary part of the progress,which every entrepreneur has to take substantial amount of risks required to make success and later to work on eliminating risks.

 

Choose Your Passion

Before watching the speech from Jeff Bezos about Amazon Amazing story, know about Jeff Bezos . Jeffrey Preston “Jeff” Bezos (/ˈbzs/;[5] born January 12, 1964) is an American Internet entrepreneur and investor. He is a technology entrepreneur who has played a key role in the growth of e-commerce[6] as the founder and CEO of Amazon.com, an online merchant of books and later of a wide variety of products. Under his guidance, Amazon.com became the largest retailer on the World Wide Web and a top model for Internet sales.[7] In 2013, Bezos purchased The Washington Post newspaper.[8]

Jeff Bezos Amazing Amazon story: Full Speech

Make it Scrum not Scrum But – Scrum free training series

Leader and his team
Scrum team

Now a days the organizations and teams who adopted to Agile and choose Scrum as a best frame-work to match with their nature of work and teams, some of the teams , scrum masters go into some misconceptions and they unknowingly fall into Scrum But instead of pure Scrum.

The below free scum training series will help you to understand the scrum framework by removing all kind of misconceptions and make it more fun way to learn about Agile/Scrum.

I have provided below the links of each session details along with the training video duration,website reference : http://scrumtrainingseries.com. These training videos are very interesting and covered the concepts with clarity and me being a Certified Scrum Master re-learned through the below training series. Hope you will enjoy going through these topics and get it into much more clarity about Scrum, thanks.

Agile Manifesto and Principles behind Agile Manifesto

In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development to define the approach now known as agile software development. Some of the manifesto’s authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto’s principles.

Manifesto for Agile Software Development

Agile Manifesto Individuals and interactions

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Principles behind the Agile Manifesto

We follow these principles:

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

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

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

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

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

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

Working software is the primary measure of progress.

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

Continuous attention to technical excellence
and good design enhances agility.

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

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

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

Reference :
http://agilemanifesto.org/history.html
http://www.agilemanifesto.org/principles.html
http://en.wikipedia.org/wiki/Agile_software_development#Agile_Manifesto