In this course, we will learn everything about Agile methodologies, we will learn about agile values & principles, then talk about agile roles like scrum master & product owner, then we will talk about the most famous methodologies like Scrum, Kanban, and Extreme programming. Also, we will talk about agile ceremonies like Daily Stand-up meeting, retrospective meeting, and Sprint review. We will learn about writing user stories & acceptance criteria. We will talk about planning for Agile projects using planning poker activity. This course will prepare you to understand everything about Agile whether you are a software developer, product owner, scrum master, software tester, or product manager.
The four values of 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.
The following 12 Principles are based on the Agile Manifesto.
1-Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2-Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
3-Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4-Business people and developers must work together daily throughout the project.
5-Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6-The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7-Working software is the primary measure of progress.
8-Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9-Continuous attention to technical excellence and good design enhances agility.
10-Simplicity–the art of maximizing the amount of work not done–is essential.
11-The best architectures, requirements, and designs emerge from self-organizing teams.
12-At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
What you’ll learn
- Agile Values
- Agile Principles
- Agile Roles
- User Story creation
- Planning Poker
- Retrospective meeting
- Daily Stand-up meeting
- Burn-down Chart
- Basic knowledge about software engineering
Who this course is for:
- Software Engineers
- Software Developers
- Software Testers
- Product Owners
- Scrum Masters