Story: What is Agile?
Agile provides an iterative framework that is used to develop software products. – UX Collective
When I took a job interview in March 2020, an interviewer talked about agile. I knew Design Sprint by Jake Knapp, but I was not clear about agile. It’s been a while, March 2022, I got a client who provides agile and scrum service in Japan. So now, I am not clear about agile, scrum and sprint.
I would like to make clear about them.
What is Agile?
©Mark Shead
– Agile = set of values and principle
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.
Agile 12 principles
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 is Agile Methodology?
©Mark Shead
– Not a methodology, more value and principle
– Scrum = framework: daily standups, sprint, product demos, retrospectives
What Is Scrum?
©Mark Shead
– Everyone has a different opinion about scrum
– Scrum is ambiguous
– Scrum = transparency, inspection, adaptation
– Scrum = roles, events, artifacts
– Scrum role = product owner, scrum master, the development team
– Scrum, terminology comes from rugby
– Scrum example = sprint, sprint planning, daily standup, sprint review, sprint retrospective,
– Product backlog, the list of things that the product owner wants
– Sprint backlog, pickup and focus on the goals
– Increment, need to be done, make a result
Scrum in under 5 minutes
©Organize Agile
– Scrum included sprint
– Work with a dedicated team
– Receive continuous feedback
– Scrum role = product owner, scrum master, team(5-7 people)
– Scrum lists = Product backlog, sprint backlog, scrum board
– 4 meetings = Sprint plan meeting, standup, review, retrospective
I was confused marketing description. If the team applies feedback to the actual product, it sounds user interview process. Maybe the car example does not fit. Physical product and manufacturing are not easy to change once production has started. SaaS may be a better example. SaaS can use the beta version before they try to get attention from public attention.
The Difference Between Agile, Scrum And Sprint
©Agile For Beginners
– Agile is a mindset, philosophy
– Agile framework(day to day action) = scrum
– Scrum = sprint is one of the methods
I could generally understand. Can I be a scrum master? That’s a different story.
Software Development Methodology: What is Agile?
©Codecademy
Waterfall refers to a sequential model for planning, building, and delivering new products and features. The requirements for any new customer experience are defined upfront and implemented in discrete phases. Each phase has specific activities that must be documented and approved before the next phase can begin. – aha.io
– How do you turn an idea into reality?
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.
– Agile = speed
– Waterfall = quality
What is Agile? | Agile Methodology | Agile Frameworks – Scrum, Kanban, Lean, XP, Crystal | Edureka
©edureka!
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.
Agile 12 principles
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.
Advantage of Agile
– Persistent software delivery
– Increased stakeholder satisfaction
– Inspect and adapt
– Welcome to changes at any stage
– Design is important
– Daily interaction
Scrum role
– Product owner
– Scrum master
– Development team
Scrum lists
– Product backlog
– Sprint backlog
– Scrum board
Conclusion: Use the knowledge and method in the work
Generally, learning is not so difficult. The issue would be how to implement values and principles to a method & actual daily work. As I said, this is for learning the client’s business. I could understand what the client doing with their customer. I can propose the content plan to consider what their customer needs.
