Agile Principles Relation To Scrum Value

Agile principles are based on an agile manifesto which has four values and 12 principles. I am trying to compare all principles concerning scrum value.

P1: “Our highest priority is to satisfy the customer through the early and continuous delivery of software.”
Key Points:
Customer satisfaction is vital for any agile project success.
Early and ongoing delivery is required to satisfy the customer.
For any business, a customer is a king. Now the question is how can we get the client satisfaction. What customer want? The answer is customer wants his good quality product ASAP.
Now the question is can we provide a full product which took two months to build can deliver in 12 days. The answer is currently no.
Now the question is how can we make the customer happy. Here is where Agile principle comes in the picture.
Associated Agile Value: “Working Software Over Comprehensive Documentation.”
Associated Scrum Value: courage, focus

P2: “Change in development as per business requirement even at the later stage.”
Key Points: Change in development as per business requirement even at the later stage.
There is a cost associated with change. Price could be time or money.
Acceptance of user/client is a key here.
Explanation: Business requirements are always changing. What today is working, tomorrow will not work. We can’t hold any change in business requirement otherwise the purpose of project/product could fail. Technology is evolving rapidly, To upscale the project to reach more consumer, it is required to change in the project by adding/changing tools and technique. If the customer has given a payment module. If you have completed it within five steps and the client asks you to reduce it up to 3 levels. It would be real business change, and we should incorporate these changes even at the later stage. It could increase the business conversion rate also for the customer.
Associated Agile Value:
“Responding to Change Over Following a Plan.”
“Customer Collaboration Over Contract Negotiation.”
Associated Scrum Value:  courage, focus

P3: “Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.“
Key Points:
Deliver software frequently even it is a piece of software.
Time to deliver software could be the 2-4 week.
Delivering software frequently means regularly getting input from the stakeholder for corrective action. We can come to know in the early stage “Are we going in the right direction?” “Are we creating the right product?”
The developer can come to know very soon that customer requirement is misinterpreted or correct. Customer’s early interaction will add more value and reduce waste. It will create ownership for both customer and development for the result.
Associated Agile Value: “working software over comprehensive documentation.”
Associated Scrum Value: courage, focus, commitment.

“Business people and developers must work together daily throughout the project.“
Key points:
Requirement generation is the work for business people and developers develop the solution for that requirement. A project can’t be initiated or completed without these people. For successful project delivery collaboration between these two people are the must.
Product owner could be business people in this case. Less interaction cause requirement ambiguity which arises chance of project failure. If business people accept the work in the shorter period, the possibility of waste regarding unnecessary work will reduce drastically. If the product owner agrees on the story in the early stage, a chance to deviate from sprint goal will decrease.
Associated Agile Value: “Individuals and Interactions Over Processes and Tools..”
Associated Scrum Value: Openness, Respect

P5: “Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. “
Key points:
A self-organized team of Motivated individuals is required to create a good project.
Project manager duty is to provide a good healthy environment and support their need. The manager should trust the team for their jobs.
Explanation: Skill is not only a factor for good productivity. The team should also be motivated in their work. The project manager needs to provide environments where:

  • The team can have a healthy discussion for any problem.
  • The team should be encouraged to deliver software on time and bug-free.
  • The team will have the right sitting plan for better interaction.
  • The team will be encouraged to have good communication with the overseas team.
  • The team will have good development software as well as hardware.

Associated Agile Value: “Individuals and Interactions Over Processes and Tools..”
Associated Scrum Value: Openness, Respect

P6: ”The most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.“

Key points:
Software development is a complicated process. An effective method of communication could be only face-face to remove waste and ambiguity.
For the remote team, it is necessary to have a Skype call (face-to-face) conversation.
Explanation: The chance of getting the correct answer with more clarity is high in face to face communication. In today world Google Hangout, Skype, etc. are available for a similar experience. Face to face communication is also very time efficient. To get a clarification over the email could take longer email thread if you compare to face to face communication. If team communicate their progress using the email instead of daily standup, everybody will receive so many emails.

Associated Agile Value: “Individuals and Interactions Over Processes and Tools..”
Associated Scrum Value: Openness

P7: “Working software is the primary measure of progress. “
Key Points:
Working software could be the subset of full software which fulfills one or two business objectives. “Working Software Over Comprehensive Documentation.”
A Primary measure of progress is working software. It could not be documentation, test cases, hardware, added resources, etc.
Explanation: End Goal of any software development is working software which is a value in this case. Working software is a business asset for the customer and for the software company it is a billable item which they charge by their delivery.

Associated Agile Value: ” Working software over comprehensive documentation.”
Associated Scrum Value: courage, focus, commitment.

P8: “Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.“
Key Points:
Sustainable development means development at the same pace.
Stakeholder, end users should work collaboratively at a constant pace to achieve a common goal.
Explanation: If development is at a very high pace, the chance of developer being exhaust is also very high. In the opposite case, development could not be that match with the business goal on time. Manager, as well as a development team, also think about upcoming leaves before committing the work. The manager also thinks about possible risk about urgent leaves and communicate to stakeholder for any blockers in advance. The team should contact immediately to business people instead of sitting idle for any requirement clarification and escalate further if it is not clarified in the first step.
Associated Agile Value: “Individuals and Interactions Over Processes and Tools.”
Associated Scrum Value: focus.

P9: “Continuous attention to technical excellence and good design enhances agility.”
Key Points: Technical excellence will speed up the development process.
Technical enhancement of the software should occur throughout the project life-cycle.
Explanation: It is a difficult question of how technical enhancement will speed up the development process. At first glance, it seems it will cause a delay in the development process. Good design will reduce the bug and make the software robust. If the developer gives attention on scalability in the initial phase of design, rework will decrease drastically.
Associated Agile Value: “Working Software Over Comprehensive Documentation..”
Associated Scrum Value: focus.

P10: “Simplicity–the art of maximizing the amount of work not done–is essential.”
Key Points: Design of the system should be simple without technical waste.
Reduce unnecessary work and emphasize on “work done.”
Explanation: In the case of software development, there would be many classes which are not required anymore or dead, remove those classes for the sake of simplicity in application design. It will reduce the overall complexity of code and speed up the development process.

Distraction on Mangement level:
Unnecessary emails and follow-ups.
Request from outside of development team.
Unnecessary meetings

Distraction on the Individual level:
Excessive Facebook engagement within the team
Multiple tea breaks
Personal Meetings in office hours

Associated Agile Value: “Working Software Over Comprehensive Documentation..”
Associated Scrum Value: courage, focus.

P11: “The best architectures, requirements, and designs emerge from self-organizing teams.”
Key Points:
Only development team knows how to create running software from the requirement.
Being the self-organized team, they can select the best architecture for the requirement and can decide who will be part of the team.
Explanation: Nobody can dictate to the team which technology, tools, and technique they will use to create the product. The team will decide the same in their internal meetings. They determine who will part of team.they check their cross-functionality as a team. Team’s decision capability make them more responsible. In traditional project management, one person(Project Manager) controls everything. This way team entirely depends on one person for everything. Too much dependency also creates a problem in the case of his absence. In agile methodologies, the whole team is responsible for the result. If any issue arises, the entire team can sit and find the solution.

Associated Agile Value: “Individuals and Interactions Over Processes and Tools..”
Associated Scrum Value: focus, respect

P12: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.”.

Key Points:
The team should be adaptive. The team can change their course of action any time according to project need. Team and the only team can take the decision how to drive the project. The team will inspect themselves and adopt the new way of working.
Explanation: The software process is not predictive. In Modern Methodologies. It is an adaptive process. The requirement is always changing. Software requirements come from business. If the modern business can’t be predictive, how can software requirement be? Waterfall model was a predictive approach where the requirement was collected in advance. Project manager creates an execution plan for this. In agile, we deliver software bit and pieces. On every delivery, the team inspects themselves, customers will give the feedback for delivery. The team will incorporate their changes in the upcoming sprint.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.