Agile Manifesto

Hi everyone, My career has changed to Product Owner 1 years ago, In previous experinece I have worked as Scrum Master also Software Engineer. In this experience I focus on only the Product Owner role. Of course I had need to changed my mind. Because when you are working as Software Engineer you need to focus on only your task. But If you become Product Owner. You would spent time for your stakholders , also you have to spend Product Vision and you have to be interested in the team for much more effort. Then you have to understand all of part of Software(Market,Customer,Software) But it is not mandatory.

Nowadays , I have decided to complete Product Owner learning path in scrum org you can find link at this?https://www.scrum.org/pathway/product-owner-learning-path

First article is absouloutely show up agile manifesto :) , I have decided to article about agile manifesto . I have talked about my experience about agile manifesto .

What is Agile Manifesto and Why?

The software industry is an environment that constantly faces changing requirements. Traditional software development processes may struggle to adapt to this rapid change. Based on these challenges, the Agile Manifesto emerged. The Agile Manifesto provides a guide to transform the software development process and embrace a faster, more flexible approach.

The emergence of the Agile Manifesto

Traditional approaches in the software industry are characterized by lengthy planning stages, rigid schedules, and strict processes. However, the lack of flexibility in this approach and the challenges of adapting to rapidly changing requirements highlighted the necessity for a new approach. This need led to the creation of the Agile Manifesto in 2001, which aimed to transform software development methods. The Manifesto was drafted by prominent software experts coming together to establish common values and principles.

The Basic Principles of the Agile Manifesto

The Agile Manifesto emphasizes four core values and twelve principles. These values are listed as individuals and interactions, working software, customer collaboration, and responding to change. Individuals and interactions highlight the importance of the human factor in the software development process. Working software emphasizes the value of a functional product over comprehensive documentation. Customer collaboration expresses the necessity of close collaboration with customers. Responding to change emphasizes the ability to adapt to rapid changes.

Twelve Principles of Agile Software

I will more detail through real experience by item by item

Our highest priority is to satisfy the customer

through early and continuous delivery

of valuable software. ->?We invested a significant amount of time on a single feature, but we were unable to fulfill all the requirements for it. After several months, we finally delivered the feature as expected by the customer. However, upon its introduction, the customer expressed dissatisfaction with the feature. This was primarily due to our failure to prioritize the creation phase with the aim of satisfying the customer. It is crucial to establish a creation phase focused on delivering valuable software in order to meet customer expectations.

Welcome changing requirements, even late in?

development. Agile processes harness change for?

the customer’s competitive advantage. ->?In one feature, It was related consent . We spent a lot of time for grooming etc. we have started to development. We almost have completed all of requirements but in the developlement section , Goverment make decision as legilation and it effect our all development. All of development have been changed according to by taken government decision

Deliver working software frequently, from a?couple of weeks to a couple of months, with a?preference to the shorter timescale. ->If you spent more than month for feature. Requirements may be changed. We faced with problem

Business people and developers must work?together daily throughout the project. ->?I cant give example. If you dont work together. You can develop software which cant be fit requirements.

Build projects around motivated individuals.?Give them the environment and support they need, and trust them to get the job done. ->?Generally We work with motivated people. Motivation and emotion are more important than technical knowledge

The most efficient and effective method of?conveying information to and within a development?team is face-to-face conversation. ->?I believe that effective communication can solve any problem. For instance, there was a situation where we started working on a task that came in through an email without fully clarifying the requirements. We failed to communicate with the owner of the requirement. As a result, we invested significant time in completing the development. However, when the owner finally saw the outcome, they expressed dissatisfaction, stating that it wasn’t what they had wanted. This scenario clearly demonstrates the impact of a communication problem.

Working software is the primary measure of progress. ->?In many sprints, we diligently measured the Scrum team’s completed story points, and everything seemed to be going well. However, after 3–4 sprints, stakeholders became increasingly dissatisfied. It became evident that our focus on story points had overshadowed the ultimate goal of delivering working software. Instead of prioritizing the tangible outcomes and value provided by the software, we had inadvertently placed excessive emphasis on the metric of story points.

Agile processes promote sustainable development.?The sponsors, developers, and users should be able?to maintain a constant pace indefinitely. ->?It is crucial to protect the outcomes of your team. Without dedicating time and effort to this, it becomes challenging to accurately measure your team’s achievements.

Continuous attention to technical excellence?and good design enhances agility. ->?In this particular development project, we had a deadline to meet for a specific feature, so our primary focus was on delivering quickly. Unfortunately, due to this time constraint, we were unable to prioritize technical excellence. Initially, when we delivered the feature, everyone seemed satisfied. However, when we started working on the second feature that relied on the previous development, we encountered technical difficulties. We found ourselves needing to rewrite code for the same area

Simplicity — the art of maximizing the amount?of work not done — is essential. ->If you dont focus simplicity , Your product will become shit :)

The best architectures, requirements, and designs?emerge from self-organizing teams. ->?If you dont create self-organized team. You have to spent much more time then excepted time for team

At regular intervals, the team reflects on how?to become more effective, then tunes and adjusts?its behavior accordingly. ->?We completed the retrospectives of our sprints, but we failed to take action on the tasks that emerged as outcomes from those retrospectives. As a result, we were unable to create a positive impact within our team.

Benefits of the Agile Manifesto

The Agile Manifesto brings forth several advantages. Firstly, it facilitates a faster and more efficient software development process. Short iterations and frequent feedback loops enable the rapid delivery of valuable working software. Additionally, it enhances customer satisfaction. Customers are actively engaged throughout the project, leading to better responsiveness to their changing needs. The Agile approach fosters teamwork and improves communication within the development team. The use of small, self-organizing teams boosts productivity and encourages creativity. Lastly, the Agile Manifesto promotes flexibility, adaptability, and the ability to respond effectively to changes. It acknowledges that change is inevitable and encourages the adjustment of processes accordingly.

Limitations and Challenges of the Agile Manifesto

The implementation of the Agile Manifesto may encounter some challenges. Adapting to changes at the business and organizational level can pose difficulties. This transformation process requires full collaboration and commitment. Additionally, it should be noted that the Agile Manifesto may not be suitable for all projects and organizations. In some cases, more traditional or non-agile approaches may be more appropriate.

We will continue for next article . Thanks for reading