Traditional to Scrum Team — Forming, Storming Norming and Performing

पारंपरिक से स्क्रम टीम — गठन, तूफान, मानकीकरण और कार्यान्वयन

The forming–storming–norming–performing model of group development was first proposed by Bruce Tuckman in 1965, who said that these phases are all necessary and inevitable in order for the team to grow, face up to challenges, tackle problems, find solutions, plan work, and deliver results. The theory remains a good explanation of team development and behavior.

Continue reading
Why Scrum: Defined Process vs Empirical Process

स्क्रम क्यों: परिभाषित प्रक्रिया बनाम आधारभूत प्रक्रिया

Most software development projects are considered complex and unpredictable in nature due to the convergence of three factors: people, requirements and technology. The various approaches used for delivering and managing projects could be more easily understood in the context of process control models and project complexity.

Continue reading
How is Scrum Related to Agile Manifesto?

स्क्रम एजिल मैनिफेस्टो से कैसे संबंधित है?

The Agile Manifesto details some fundamental agile philosophies, one of which is a preference for Empirical Process control — which maintains that knowledge is derived from experience and decision making is based on what is known. Scrum is an Empirical Process based on inspection, adaptation, and transparency. gave the name “Agile” to the movement.

Continue reading
The Brief of History of Scrum

स्क्रम के इतिहास का संक्षिप्त विवरण

The history of the Scrum method starts in 1986. That year, two Japanese business experts introduced the term in the context of product development. Hirotaka Takeuchi and Ikujiro Nonaka published the article, “New New Product Development Game” (the double “New” is indeed part of the title) in the Harvard Business Review. The authors described a new approach to commercial product development that would increase speed and flexibility. Their inspiration came from case studies from manufacturing firms in the automotive, photocopier, and printer industries.

Continue reading
Scrum Product Owner: The Role and Responsibilities

स्क्रम प्रोडक्ट ओनर: भूमिका और जिम्मेदारियाँ

A Product Owner is responsible for telling what should be developed and the order of items that needs to be fulfilled. You can consider him as the sole authority that would tell the rest of the team what they need to create and which features should come first. In short, he is the one who tells the other members of the team about what they should be coming up with.

Continue reading