Agile History(Agile Manifesto/Principles)

https://amagiletester.blogspot.com/2015/11/agile-historyagile-manifestoprinciples.html

Lets take you to the History of Agile ,Manifesto and Statement of Principles.

History of Agile:

            The revolution against the "Heavy Weight" software development processes was started in 1990. New methods were being invented to come out of hectic processes.

   In 2001, seventeen(17) people grouped in UTAH to find a common ground which will ease of development process.They discussed their experiences with different processes they are following and grind them to develop a Manifesto for Agile. They call the meet as "Agile Alliance".

Agile Manifesto: To expose the developing software Agile Alliance developed a Agile Manifesto as follows: 

1. Individuals and interactions over processes and Tools.
2. Working Software over Comprehensive documentation.
3. Customer collaboration over contract Negotiation.
4. Responding to change over following a plan.

Statement of Agile Principles: Following the above four values,derived 12 principles of statement . we will see what are those interesting principles.

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale
3. Working software is the primary measure of progress.
4. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
5. Business people and developers must work together daily throughout the project.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. The best architectures, requirements, and designs emerge from self-organizing teams.
8. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
9. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
10. Continuous attention to technical excellence and good design enhances agility.
11. Simplicity -- the art of maximizing the amount of work not done -- is essential.
12. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 

I know some of the principles are Employee friendly and esp less maintained by companies. 

What i learned being working in Agile team is "Be bold", confident to say what you worked and issues you are facing with either team or with scrum master or who ever. 

This may look silly but raise the voice.Self respect is the most important character a person should have. So don't hesitate to respond when you think you are loosing your self respect.

I suggest some of the tips in order to overcome the challenges in the Team. This is my self experience and what i follow:

Do what you say. No matter how small the task, if you tell someone you will do something, do it.

Admit when you are wrong. Everyone makes mistakes. When you make a mistake, admit to it and make it right.

Follow up. Follow up on open issues that take some time. This allows people to see that you have not forgotten them.

Cheers :) Navatha Kannadi