
Explore agile fundamentals through theory and hands-on practice with Jira, covering values, principles, roles, user stories with acceptance criteria, and product backlogs, plus interview prep and PMI agile exam readiness.
Explore the agile four values—individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan.
Explore the agile 12 principles rooted in four values, prioritizing early and continuous delivery of valuable software to satisfy the customer, with working software as the progress measure.
Compare waterfall and agile development, highlighting fixed requirements, time, and resources in waterfall, versus fixed time and resources with estimated requirements in agile, enabling feature delivery within set time.
Learn how to write user stories from the perspectives of developers, testers, and business reps, including acceptance criteria, given-when-then format, and definition of done.
learn to set up an agile project in jira by signing up, choosing the software scrum project with the classic template, and writing a user story for a demo project.
Organize Jira projects by managing the backlog and prioritizing issues, using epics, stories, tasks, and bugs to plan releases.
Learn to decompose agile requirements from theme to user tasks, detailing theme, epic, feature, epic user story, and user story, and map tasks across development, testing, and deployment.
Discover how scrum uses fixed-length sprints to deliver a product increment and gather feedback. Learn backlog refinement, sprint backlog, and daily scrums with planning poker and Fibonacci-based estimates.
Discover the three core scrum roles—product owner, scrum master, and development team—and their duties, including product backlog management, backlog item prioritization, and transparency of the backlog.
Start the sprint, set duration, and manage the login functionality epic on the scrum board, moving stories and defects to completion and reviewing the burn-down chart.
Explore how burn-down charts track story points against sprint progress, illustrate expected versus actual completion, and manage backlogs by adjusting remaining work.
Explore how the velocity chart visualizes work completed across sprints, defines team velocity in story points, and uses multiple iterations to estimate future sprint capacity and plan work.
Evaluate performance in end-of-sprint retrospectives to identify improvements for future iterations; a scrum master uses a sticky-note board to pick one continue, one stop, and one start item.
Discover extreme programming, an agile methodology for software teams that emphasizes development and testing, continuous integration, pair programming, simple design, short iterations, and the 12 XP principles.
Discover the 12 extreme programming principles, from the planning game and customer collaboration, small releases, system metaphor, simple design, continuous testing, refactoring, pair programming, collective code ownership, and continuous integration.
Compare agile methods—scrum, xp, and kanban—highlighting xp's development and testing focus and slack changes, versus scrum's management focus and fixed sprints. Kanban adds visualization with optional timeboxing.
Learn the seven types of agile planning—from product vision and roadmap to release planning, sprint planning, daily scrum, and sprint review and retrospective—and how teams deliver iterative releases.
Explore lean software development as a mindset that eliminates waste and improves flow of work. Learn seven waste types, amplify learning, and empower the team with fast delivery.
Understand kanban as a visual workflow tool that uses a board with columns like to do, doing, and done, enforcing work in progress limits to improve lead time.
Explore agile tools with Trello and template boards to manage work using Kanban and sprints. Learn to pick a suitable tool, create boards, and apply templates for backlogs and projects.
Learn to create a Trello board, structure it with lists and cards in a kanban workflow from requirements to maintenance, customize privacy, invite members, and attach UI references.
Explore Agile Manifesto values and principles, and key scrum concepts like sprint, sprint backlog, product backlog, and product increment.
Prepare for the PMI certified agile practitioner exam by inspecting and adapting plans to schedule changes, ensuring transparency with the product owner and collaborating with stakeholders to maximize backlog value.
Agree on a definition of done for each work item to prevent conflicts, and add mid-sprint bugs to the backlog for the next iteration.
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.