The Agile Manifesto 1-2

Nextgen Academy
A free video tutorial from Nextgen Academy
International Agile Project Consultant
3.7 instructor rating • 1 course • 20,223 students

Learn more from the full course

Your complete guide to Agile, Scrum, Kanban

Scrum Master certification training + Agile Scrum Training + Scrum Product Owner training

02:53:28 of on-demand video • Updated May 2019

  • At the end of this course, students will easily be able to practically apply each 12 steps of the Agile Manifesto
  • Learn to differentiate and understand risks and pitfalls in an Agile environment and how to overcome them
  • At the end of the course, students will be able to practically apply their your new Scrum Master and Kanban knowledge to lead teams through production sprints
  • Students will be able to demonstrate a deep knowledge in Project Planning as well as risk mitigation
  • Students will be able to add value to their organization through learning about Business Value in an Agile environment
  • You will be able to foresee risks and demonstrate excellent problem solving skills using different methods
English [Auto] The first principle of agile says our highest priority is to satisfy the customer to early and continuous delivery of valuable software. Your goal here is to focus on delivering value whether it's software or designs or an organizational plan forward the means by how you do this. Scrum Master ceremonies and for instance different tools are just tools should you not reach your goal. Due to complex tools and processes there's obviously a bottleneck and needs to be cut or set aside in Agile. Will you deliver to have a level of agreed usability. This means that in a small amount of time you agree on a deliverable. Let's see your first sprint. He should deliver the highest business value to the product. You may not be perfect but needs to follow a trajectory of iterative processes that make the public pull. Well the first month that helps you do the delivery improve the work allow customers to evaluate the value you brought to the table and give points of feedback as well as opening up for more communication with the team declined for the organization. Here's where we again refer back to waterfall project management reclining contact usually happens at the start at the end of the project. Continuous delivery can be challenging in these environments from breaking down work and deliver a future incrementally helps delivering pieces the projects the customer so that they receive value. The second principle of agile says welcome changing requirements. Even leading in the developed Agile processes harness change for the customer's competitive advantage. The second principle addresses a concept that traditional project management methods can adapt to change in the software world. But within an organization change of scope or details in a product often come with all sorts of risks such as missing and important clients that deadline or going over your budgeting forecasts. The reason you need to embrace change is to provide value. The changes does not provide value of any sorts. Why would you do it. Well sometimes our customer's orientation towards our goals change. Sometimes they also don't completely understand their needs until seeing the first incremental piece of value being delivered from both parties or even within organizations stakeholders focus on value and have that mindset across the entire project. Change will come so difficult. Also taking a navigational approach rather than its done approach means that you might get to a better destination and yet be prepared to change direction and find advantages for the people we work with. Besides change may open up more opportunity for you and the teams do excellent work.