Agile is a philosophy and a way of thinking that's guided by 4 values and 12 principles.
As a mindset over a framework, process, or methodology.
Agile Values
Value #1: Individuals and Interactions over processes and tools
Value #2: Working software over comprehensive documentation
Value #3: Customer collaboration over contract negotiation
Value #4: Responding to change over following a plan
Agile Principles
Principle #1: Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software
Principle #2: Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage
Principle #3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
Principle #4: Business people and developers must work together daily throughout the project.
Principle #5: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Principle #6: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Principle #7: Working software is the primary measure of progress.
Principle #8: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Principle #9: Continuous attention to technical excellence and good design enhances agility.
Principle #10: Simplicity, the art of maximizing the amount of work not done is essential
Principle #11: The best architectures, requirements, and designs emerge from self-organizing teams.
Principle #12: At regular intervals, the team reflects on how to become more effective. Then tunes and adjusts its behavior accordingly.
Benefits of using Agile
Allows to deliver that value in smaller increments to the customer
Iterative process, the team is able to get feedback on their performance as well
Challenges of using Agile
The company is applying Waterfall
Agile lack document, Agile focuses on communication than writing requirement.
Not a clear role that takes control or has ownership of the project.
Topic 4: Scrum Methodology: Scrum Terms and Artifacts
User stories
Acceptance Criteria
Great User stories
User stories example
Product backlog & Sprint backlog
Product backlog
Sprint backlog
Working agreements (Terms)
Definition of Ready
Definition of Done
Product Increment
Topic 3: Scrum Methodology: Scrum Ceremonies and Events
Daily Stand-Up Meeting
Sprint Planning Meeting
Sprint Review Meeting
Sprint Retrospective
Product Backlog Grooming
Topic 2: Scrum Methodology: Overview, Values and Roles