A burn up chart tracks progress towards a projects completion. In the simplest form of burn up chart there are two lines on the chart: · A total work line (the project scope line) · A work completed line A burnup chart clearly shows both completed work and project scope. The project will be completed when the […]
Read MoreThe Primary Team roles in scrum are named as • Product Owner • Scrum Master • Development Team Scrum Master, Product Owner, and Team are considered as people who are committed to the project while customers and executive management are considered as involved but not committed to the project. Scrum Teams are self-organizing and cross-functional. […]
Read MoreStory Point Estimation is a “Relative Estimation Technique”. This is one of the popular estimation technique used in Scrum implementations. The meaning of Relative is that we assign a point value to each item. The raw values we assign are unimportant. What matters are the relative values. A story that is assigned a 2 should be […]
Read MoreThe 3-Question format is the most popular format for Daily Scrum. The 3 questions focus on 3 things What did I do yesterday which helped the team get closer to the sprint goal? What will I do today which will help the team get closer to the Sprint Goal? Are there any impediments which will […]
Read MoreUser story is one of the popular way of writing requirement in Agile. Lot of Agilists prefer the User Story format. However, that is not the only way of writing requirements in Agile projects. You could write requirements in many ways, for e.g.Use Cases, Business Requirement Specification, BDD etc Scrum is a framework. That means, […]
Read MoreIn Continuous integrations, all the developer work is merged to main branch several times a day. This helps in reducing integration problems. In Continuous integration we try to minimize the duration for which a branch remains checked out. A developer code gets early feedback on the new code added to main repository by using Continuous Integration. […]
Read MoreKanban is a visual process and project management tool first developed in Japan by Toyota. Kanban is a way to visualize your work and limit the amount of work in progress at any one time. KanBan is often seen as a central element of “Lean” manufacturing and is probably the most widely used type of […]
Read MoreExtreme Programming (XP) Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent “releases” in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be […]
Read MoreThe User Story is the most granular unit of requirement on a Scrum Project. The Product Owner writes the User Stories. The Sprint Backlog gets elaborated into User Stories when the Sprint Planning is done. It is important to note that the user story is a medium that helps in Gathering basic information about requirements Records high level […]
Read MoreDone Criteria are a set of rules that are applicable to all User Stories. A clear definition of Done is critical because it removes ambiguity from requirements and helps the team adhere to mandatory quality norms. This clear definition is used to create the Done Criteria when a Prioritized Product Backlog is prepared. A User Story is considered […]
Read More