Introduce about AGILE Tran Duc Tien The Agile

Introduce about AGILE Tran Duc Tien

The Agile Manifesto Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over contract negotiation Responding to change over Following a plan

Twelve Principles of Agile Manifesto 1. Customer Satisfaction 2. Welcome Change 3. Deliver a Working Software 4. Collaboration 5. Motivation 6. Face-to-face Conversation 7. Measure the Progress as per the Working Software 8. Maintain Constant Pace 9. Monitoring 10. Simplicity 11. Self-organized Teams 12. Review the Work Regularly

Advantages of Agile ü ü ü Change is embraced End-goal can be unknown Faster, high-quality delivery Strong team interaction Customers are heard Continuous improvement

Disadvantages of Agile × × Team must be knowledgeable Time commitment from developers Documentation can be neglected Final product can be very different

Agile Development Cycle

Differences and Similarities: Waterfall vs Agile

When You Should Use Waterfall and When to Use Agile?

Agile Frameworks 1. 2. 3. 4. 5. 6. 7. 8. SCRUM EXTREME PROGRAMMING (XP) KANBAN Feature-driven development (FDD) Dynamic Systems Development Method (DSDM) Adaptive system development (ASD) Lean Software Development (LSD) Crystal Clear

SCRUM OVERVIEW Product Owner User story A The Product Owner gets the product requirements from the customer (End Users, Executives or other stakeholders). User story B User story C User story D User story E User story F Product Backlog Product Owner adds the right user stories to the Product Backlog - the ultimate wish list for making the product awesome!

Communicates Business Scrum team Product Owner decides what user stories should be given the most priority, s/he defines acceptance criteria and communicates business requirements to the Scrum team. Backlog Refinement Also called Product Backlog Grooming is a meeting of the Product Owner and the Team Members for the purpose of ensuring that the product backlog contains only suitable items in order of priority. Questions from team members are also attended this time.

This is when the Scrum Master facilitates a meeting between the Product Owner and Development Team to determine what needs to be completed in the next sprint. Sprint Planning 24 h Sprint cycles A 15 -minute meeting called the Daily Scrum is usually held at the start of the day for the purposes of making sure members of the development team are on the same page. Scrum Master Sprint cycles of no more than 4 weeks Ideally between 2 -3 weeks

Feature A Feature B Feature C Total product backlog items to be delivered at the end of each Sprint. Potentially Shippable Product Sprint Retrospective A discussion on what went wrong during the last sprint and how the next sprint could be improved. Finally, through incremental product releases, the Product Owner is able to deliver value to the customer. Product Owner

ROLE BREAKDOWN Product Owner Interfaces with the customer and the scrum team. Scrum Master All through the process, the scrum master ensures that the project processes smoothly by checking to see team members have the right tools and everyone is working in strict adherence to Scrum principles. Scrum Team Developer Business Analyst Tester Communicator

SCRUM DOCUMENTS (Artifacts) Burn down charts This is a graphical representation of the progress made during a sprint. It clearly shows the amount of work left to do and the amount of time left to do it. It helps to predict when the work will be completed. User story A User story B User story C User story D User story E User story F Feature A Feature B Feature C Sprint Backlog Product Backlog Contains the highest priority user stories to be completed during the Scrum sprints. Prioritized list of features

SCRUM EVENTS Backlog Refinement Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

Advantages of Scrum ü ü More transparency and project visibility Increased team accountability Easy to accommodate changes Increased cost savings

Disadvantages of Scrum × × Risk of scope creep Team requires experience and commitment The wrong Scrum Master can ruin everything Poorly defined tasks can lead to inaccuracies

Extreme Programming

KANBAN

Preferences • https: //www. smartsheet. com/agile-vs-scrum-vswaterfall-vs-kanban • https: //www. istqb. org/downloads/category/5 -agile -tester-extension-documents. html • https: //www. tutorialspoint. com/scrum/index. htm • https: //www. tutorialspoint. com/extreme_program ming/index. htm • https: //www. tutorialspoint. com/kanban/index. htm

Thank you! • Q&A • Next presentation