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

Principles of Agile Methods

Customer Collaboration

  1. Users should work closely with the development team.

  2. Users should provide feedback on the system and suggestions for requirements/improvement.

    Embrace Change

  3. Changes to the requirements can happen at any time during the development.

  4. Plans can quickly become inaccurate with the rapid change to the requirements.

    Incremental Delivery

  5. It is more important to deliver the software than following the plan.

  6. The software should be developed incrementally and iteratively with each delivery having more functionalities included.

    Maintain Simplicity

  7. Keep everything simple, for both the software and the software process.

  8. Focus on delivering valuable software to the customer rather than writing comprehensive documentation.

    People, not Process

  9. Focus on the people on the team. Tools and practices are second.

  10. People should be left to develop their own ways of working, rather giving prescriptive processes.
  11. Exploit and explore skills and knowledges of team members and trust them.

    eXtreme Programming (XP)

    “XP is a style of software development focusing on excellent application of programming techniques, clear communication, and teamwork…”
    Principles: “A set of complementary principles, intellectual techniques for translating the values into practice…”
    Practices:”A body of practices proven useful in improving software development.”
    Values: “A philosophy of software development based on the values of communication, feedback, simplicity, courage, and respect.”

XP Principles

  1. Humanity
    1. Balance the needs of the individual with the needs of the team
  2. Economics
    1. The time value of money
    2. The option value of systems and teams
  3. Mutual Benefit
    1. Every activity should benefit all concerned
    2. Write automated tests that help the design and implementation better today; leave the test as the ‘documentation’ for future programmers
    3. Refactor to improve simplicity, clarity and coherence
  4. Self-Similarity
    1. Use the structure of one solution into a new context, even at different scales (it’s a good place to start)
  5. Improvement
    1. Get an activity started right away, then refine the results over time.
  6. Diversity
    1. Programmers should work together on the problem and all opinions should be valued
  7. Reflection
    1. Review and analyze why they succussed or failed
  8. Flow
    1. Continuous flow of activities rather than discrete phase (small increments, continuous integration)
  9. Opportunity
    1. Seeing problems as opportunities for changes (personal growth, deepening relationships, and improved software)
  10. Redundancy
    1. Difficult problems in software development should be solved in several different ways.
  11. Failure
    1. If you have 3 ways to implement a user story, but you don’t know which to use, try all of them
  12. Quality
    1. Quality can be measured in defect, design quality, and the experience of development
  13. Baby Step
    1. Proceeds one test at a time, and integrates and test a few hours’ worth of changes at a time
  14. Accepted Responsibility
    1. Responsibility cannot be assigned; it can only be accepted

XP Workflow

  1. At the beginning of the project development, the product manager and the user write Stories (programmers may also be involved).
  2. The programmers estimate the stories and tasks.
    1. if a story is too big, the product manager and/or the user split the story; if the programmers don’t understand the topic, initial a Spike.
  3. The product manager and/or the user decide on a “theme” (the big picture) for a Quarterly Cycle.
    1. The process iterates until the project finishes.
  4. The product manager, the users and/or the programmers pick a reasonable number of user stories for Weekly Cycle and add some Slacks.
    1. The process iterates until the end of the Quarterly Cycle

XP – Planning the Release

XP Programmer Workflow

Scrum

A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Transparency :

  1. Process must be visible to all team members.
  2. Use common language and share a common definition.

Inspection:

  1. Scrum artifacts and progress must be inspected frequently without interfering team’s work.

Adaptation:

  1. If a process or development deviates outside the plan, adjustment must be made in time.
  2. Use an iterative and incremental approach to control risk.
  3. Make decisions based on what is known.

The Components of Scrum Framework
Values: The Scrum team members learn and explore the value of commitment, courage, focus, openness and respect as they work with the Scrum roles, events, and artifacts.
Team: A typical Scrum Team includes a Product Owner, the Development Team, and a Scrum Master.
Events: Four formal events are common to all Scrum teams, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Artifacts:
• Product Backlog
• Sprint Backlog
• Portfolio Backlog
• Program Backlog
Rules: Binding all components together

Scrum Workflow — Vision
— Product Backlog Management
— Sprint Planning

Manage User Stories in Sprint Backlog
Scrum Workflow – Sprint
— Daily Scrums
— Sprint Review
— Sprint Retrospective

DevOps