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

Comments

  1. Sourabh PandeyMarch 22, 2021 at 4:04 AM

    Thank you Rocky, you can see more of my posts at https://m.facebook.com/BuildingMarketReadyAgileProfessionals

    ReplyDelete
  2. GraphicsOctober 23, 2021 at 6:33 AM

    You’ve got some interesting points in this article. I would have never considered any of these if I didn’t come across this. Thanks!. Offshore development services

    ReplyDelete

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more