top of page
Admin

1- The Agile Manifesto and Scrum.


scrum

If you haven't heard it before, you'll probably hear the word a lot in the future. So let's pause for a moment to understand what Agile actually refers to. Most often, Agile describes a methodology in which business requirements and potential solutions emerge through the collaborative effort of cross-functional, self-managing teams and their customers or end users. The term 'agile' in this context comes from the Manifesto for Agile Software Development, which you can find as a resource to this lecture. The values ​​and ideas in this manifesto were derived from a broader range of frameworks, including Scrum, Kanban, Crystal, Extreme Programming, and many others. This is why Scrum is considered an agile framework and associated with the Agile movement. But let's take a look at what the manifesto says.


We are unlocking better ways to develop software by doing it ourselves and helping others do it. Through this work, we have come to value these values:


Individuals and interactions more than processes and tools. Let's think about what that means. Having well-established processes and using the right tools is undoubtedly important. But even more important is having skilled and dedicated people working together toward a common goal.


Working software more than comprehensive documentation. The main purpose is to create a working product, not tons of documentation. Documentation is useful when used carefully, but it shouldn't be the focus. You can't do much with documentation alone if you don't have a product to use.


Collaborating with the client more than negotiating a contract. When dealing with clients, you want to collaborate and have a common purpose or goal. You want to build trust and have a working relationship where both parties help each other move forward. You don't want a relationship where you're dealing more with lawyers and contracts than with the actual client themselves.


Responding to change more than following a plan. Having a plan is important. If the plan is rigid, it will be difficult to respond to changes in the market or new technological developments. Be prepared to adapt your plan when necessary. The more flexible you are, the better. Think about how agile squirrels are. They may have a plan in mind, but often they need to react quickly, really quickly. Their typical reaction time is around 100 milliseconds. That's agile.


I would strongly recommend reading the Agile Manifesto and the principles behind it. Although the Agile Manifesto is now over 20 years old, the ideas and principles apply not only to software development, but to other product categories as well.


Scrum existed before the Agile Manifesto was created in 2001. The term Scrum was used in the context of product development as early as 1986. It wasn't until 1995 that Ken Schwaber and Jeff Sutherland presented a paper describing the Scrum framework. To this day, they remain known as the creators, promoters, and maintainers of what has become the Scrum framework.


If you read the Agile Manifesto carefully, you will notice that the names of the Scrum creators appear among those who initiated the Agile movement.



 

Udemy-Courses

1 view0 comments

Comentarios


bottom of page