Module 1 - Agile Manifesto

Key Takeaways

in 2001 a group of software developers got together the Snowbird resort in Utah and agreed the manifesto for agile software development in this they came up with four value statements and twelve principles underpinning those value statements the manifesto is surrett that we're uncovering better ways of developing software by doing it and by helping others do it this led to four value statements individuals and interactions over processes and tools working software over comprehensive documentation customer collaboration over contract negotiation and responding to change over following a plan the statement that while there is value with items on the right but we value items on the left more is often either forgotten or devalue to the part in assets of the myths this agile doesn't do tools a job doesn't do documentation agile doesn't do contracts and agile doesn't follow any plans in reality I'm Joel and scrum is a living plot based in a 24 hour cycle the sprint cycle and the product cycle the Sprint goal the sprint plan provides vision a transparency over what will be delivered in this bring in a far greater way than the stage plan has done under prints to the artifacts is grown included the product backlog sprint backlogs and done increment provides sufficient clarity for the product under development however where documentation is required to share information with stakeholders or for the development team to understand and share how to deliver an item then they should be provided the events present scrum concluding sprint planning daily scrum sprint review and the retrospective for many opportunities for individuals and the interactions to build clarity to understand how and what should be developed although there was many benefits to the application lifecycle management tools and the platform tools such as puppet care should be taken that these are not used to replace inspect and adapt opportunities between the individuals and interactions