Scrum Roles allows teams and organizations to iteratively and incrementally deliver valuable products of “Done” working releasable software within a Sprint. Key focus areas are Product Owner, Development Team & Scrum Master in a Scrum Team. Scrum Roles Scrum defines three roles: Scrum Master, Product Owner, and Developers. There are no other roles like project […]
Scrum Roles – Scrum Framework Read More »
Definition of Done is an agreement between Development Team and the Product Owner on what needs to be completed for each user story so that it can be satisfactorily verified and validated – usually in the form of a clear and concise list of acceptance criteria that a software Increment must adhere to for the
Definition of Done – Importance in Agile Read More »
3C’s is an Effective User Story technique. 3Cs: Card, Conversation, and Confirmation. The Card is the index card that the User Story is written on. The index card format serves two purposes: To write requirements on index cards, each requirement has to be small and self-contained; this helps us focus on what we need to do for
Effective User Story – Card, conversation, confirmation Read More »
INVEST, DEEP , SMART & Three C’s are Effective User Story Techniques. INVEST is a useful mnemonic established by Bill Wake in Extreme Programming Explored. It can be used to inspect the quality of your user story by validating it against each of the following (in Bill Wake’s words): Effective User Story Techniques – INVEST Independent – Each User
Effective User Story Techniques INVEST DEEP SMART 3Cs Read More »
Planning Poker is a consensus-based technique for estimation, mostly used to estimate effort or relative size of development goals in software product development. Planning Poker is done with story points, ideal days, or any other estimating units. The Scrum Master, Product Owner, and the development team participate in Planning Poker activity. Purpose: Estimate the effort
Planning Poker – Agile Estimation Method Read More »
A user story describes how the user will use the software in just a few sentences. User stories can be used to represent a new feature, an enhancement to an existing feature, a technical task (like a nonfunctional requirement), or a defect unearthed during testing. As a < type of user >, I want <
User Story – How to write effective user stories Read More »
