agile

Summary From user stories to Acceptance Criteria (AC) with Behaviour Driven Development(BDD)

Summary ref: https://www.youtube.com/watch?v=Va_93ygTnOs BDD is not a testing tool, but a colaboration tool. ref: https://www.youtube.com/watch?v=6nSwRSbc27g Dan North is the orginator of BDD. According to him BDD is TDD, he just removed the word Testing to get buy in of people. Difference between TDD and BDD They are....

Summary? Use Cases, introduced by Ivar Jacobson more than 20 years ago, are used to capture user (actor) point of view while describing functional requirements of the system. They describe the step by step process a user goes through to complete that goal using a software system. Simple Use Case Diagram A Use Case is a description of all the ways an end-user wants to “use” a system. Use Cases capture all the possible ways the user and system can interact that result in the user achieving the goal....

Definition ref: link The Technical Debt means additional rework caused by implementing limited, temporary solutions or incomplete work. I also count as technical debt: code not deployed up to the environment, whichmakes it available to the users, features developed but not documented or tested. When done, the output of a story must be ready to be released. If it is not, everything pending is called technical debt.

Summary Difference between Definition of Done (DOD) vs Acceptance Criteria (AC)? Num Definition of Done (DOD) Acceptance Criteria (AC) 1 Generic(common) Specific 2 Abstract Concrete 3 Requirements to adhere Test scenarios ref: link Definition of Done (DoD) is a list of REQUIREMENTS that a user story MUST ADHERE to for the team to call it complete. While the Acceptance Criteria of a User Story consist of set of TEST SCENARIOS that are to be MET to confirm that the software is working as expected....

Summary ref: link According to Kent Beck and Martin Fowler stories(User Stories) and features are SYNONYMS: A user story is a chunk of functionality (some people use the word feature) that is of value to the customer. What you call a feature is usually referred to as theme or epic. Themes and epics are used to group user stories to bigger feature sets, that make sense on their own. From a more semantic point of view: feature is a part of the system you are trying to build, user story is a way to describe that part....