https://jaaved.netlify.app/tags/agile/Recent content in agile on Jaaved Ali KhanHugo -- gohugo.ioen-usMon, 28 Aug 2023 20:57:08 +0400https://jaaved.netlify.app/notes/202103251707-use_cases/Mon, 28 Aug 2023 20:57:08 +0400https://jaaved.netlify.app/notes/202103251707-use_cases/https://jaaved.netlify.app/notes/202103251314-user_stories/Thu, 30 Mar 2023 13:34:03 +0300https://jaaved.netlify.app/notes/202103251314-user_stories/https://jaaved.netlify.app/notes/202103272001-definition_of_done_dod/Sat, 14 Jan 2023 20:22:31 +0400https://jaaved.netlify.app/notes/202103272001-definition_of_done_dod/Definition # ref: link Scrum defines the Definition of Done in pretty simple terms: it’s the acceptance criteria that are common to every single user story. The definition of “done” depends on the task. In Agile Software Development, we use the User Story Definition Of Done(DOD) for User Stories to ensure the quality of work and to assess whether the team completes a User Story or not. If respected, the Definition of Done (DOD) in Scrum is keeping the development team away from the .https://jaaved.netlify.app/notes/202103281429-difference_between_user_story_and_feature/Sat, 14 Jan 2023 20:18:34 +0400https://jaaved.netlify.app/notes/202103281429-difference_between_user_story_and_feature/Summary # ref: link According to Kent Beck and Martin Fowler 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.https://jaaved.netlify.app/notes/202103272011-technical_debt/Sat, 14 Jan 2023 20:13:56 +0400https://jaaved.netlify.app/notes/202103272011-technical_debt/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.https://jaaved.netlify.app/notes/202103251452-gantt_chart/Sat, 14 Jan 2023 20:12:45 +0400https://jaaved.netlify.app/notes/202103251452-gantt_chart/https://jaaved.netlify.app/notes/202103272020-difference_between_definition_of_done_dod_and_acceptance_criteria_ac/Sat, 14 Jan 2023 20:11:10 +0400https://jaaved.netlify.app/notes/202103272020-difference_between_definition_of_done_dod_and_acceptance_criteria_ac/Summary # Difference between vs ? Num 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.https://jaaved.netlify.app/notes/202103271957-acceptance_criteria/Sat, 14 Jan 2023 20:10:42 +0400https://jaaved.netlify.app/notes/202103271957-acceptance_criteria/Definition # ref: link Acceptance criteria are a set of statements that describes the conditions a software product or a project deliverable must satisfy in order for the User Story to be accepted by a Product Owner, user, customer, or other stakeholder. Acceptance criteria are incredibly important in Scrum because they spell out what a development team needs to accomplish for a given Sprint. Whenever a user story is written the product owner and the team collaborate to determine the AC of the story.https://jaaved.netlify.app/notes/202103271948-from_user_stories_to_bdd/Mon, 04 Apr 2022 10:33:07 +0300https://jaaved.netlify.app/notes/202103271948-from_user_stories_to_bdd/Summary # From user stories to Acceptance Criteria (AC) with Behaviour Driven Development(BDD)https://jaaved.netlify.app/notes/202103271745-behaviour_driven_development_bdd/Mon, 04 Apr 2022 10:32:56 +0300https://jaaved.netlify.app/notes/202103271745-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. The key difference is the scope. TDD is a development practice while BDD is a team methodology. In TDD, the developers write the tests while in BDD the automated specifications are created by users or testers (with developers wiring them to the code under test.