What is the Problems of Waterfall Model?

مشکلات مدل آبشاری چیست؟

In reality, customers may not know what their needs are until they see the software at work, so changing their requirements leads to redesign, redevelopment and retesting, and increased costs. Developers may design a new software product or feature without realizing the difficulties ahead, in which case it is better to modify the design rather than insist on a design that does not take into account any newly discovered constraints, requirements, or problems. As a result, there is no guarantee that the requirements the organization has in mind will actually work.

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
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