یادگیری یک چیز جدید هر روز
The Definition of Readiness (DOR) records when a product backlog item (such as user stories) has worked to the point where it is “likely” to be included in a sprint, while the Scrum team uses DoD to define when all work on a product backlog item (such as user stories) has been completed.
Continue reading
Scrum artifacts provide critical information that the Scrum team and stakeholders need to know in order to understand the product being developed, the activities being planned, and the activities being completed in the project. The following artifacts are defined in the Scrum Process Framework.
Continue reading
The completion definition (DoD) is a list of requirements that the user story must comply with so that the team can invoke it as complete. The acceptance criteria for user stories include a set of test scenarios that will meet the requirements to confirm whether the software works as expected.
Continue reading
It’s important to prioritize your product backlog to make sure it doesn’t become an open-ended list where everyone has random ideas about your product. Your to-do list needs to be structured, organized, and prioritized to identify the most strategically important things for your team to do. In this article, I introduce the 100 Points method for product backlog refinement activities.
Continue reading
Scrum compares a software development team to a football team. It has a clear and highest goal, is familiar with the best model and technology required in the development process, has a high degree of autonomy, close communication and cooperation, and ensures to solve various challenges every day with a high degree of flexibility; Each stage has a clear progress towards the goal.
Continue reading
The product backlog lists all the features, functions, requirements, enhancements, and fixes required for the product releases. Product backlog projects have the attributes of description (appropriately Detailed), story points (Estimates), and orders (Prioritized). They must be continuously added, deleted, and updated (Emergent) in the backlog, and reflect the understanding of the team backlog in a timely and appropriate manner .
Continue reading
Scrum originated in software development projects, but it is suitable for any complex or innovative projects. Scrum has been used to develop software, hardware, embedded software, interactive function networks, autonomous driving, schools, governments, markets, management organizations and operations, and almost everything we (as individuals and groups) use in daily life.
Continue reading
The 2020 Scrum Guide contains numerous updates and changes that there are seven major changes from the 2017 edition to the 2020 edition
Continue reading
Agile development is a human-centric, iterative, and gradual development method. In agile development, the construction of a software project is divided into multiple sub-projects, and the results of each sub-project have been tested and have the characteristics of integration and operation. In other words, a large project is divided into multiple small projects that are interrelated but can also be run independently, and completed separately. During this process, the software is always in a usable state.
Continue reading
LeSS is a lightweight, Agile framework for scaling Scrum to more than one team. Starting in 2005 Bas Vodde and Craig Larman developed the LeSS framework after using Scrum principles and rules on large scale projects. Their goal was to develop large scale projects successfully while staying within the constraints of Scrum.
Continue reading