Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
The Agile Manifesto2:37 with Matt Anthes-Washburn
The Agile Manifesto encourages teams to think about how to break down the silos that separate people working on a project, giving people formal roles and responsibilities and providing expectations for collaboration.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Silo An analogy for the negative effects of specialization and departmentalization in organizations. In agriculture, grain is stored in series of tall silos that compartmentalizes the grain. In an organization, a silo occurs when a specialized group does not communicate with other groups, or silos. The opposite of siloing is collaboration.
So in 2001, a group of 17 software developers, 0:00 interested in developing software using less resources and less time, gathered 0:03 to discuss taking a new philosophical stance on software development. 0:09 They composed what they called the Agile Manifesto, with the intent of promoting 0:13 software development methods that are nimble and able to respond to change. 0:18 In the Agile Manifesto, these authors outline several guiding values, 0:23 saying that while they value the things on the right, 0:28 they value the things on the left even more. 0:30 First, the Agile Manifesto declares the value of individuals and 0:33 interactions over processes and tools. 0:37 You may have seen in our discussion of waterfall that each group was confined to, 0:41 or siloed in their own areas of expertise. 0:46 The Agile Manifesto encourages teams to think about how to break down the silos 0:49 that separate people working on a project, giving people formal roles and 0:54 responsibilities, and providing expectations for collaboration. 0:58 The second value is of working software over comprehensive documentation. 1:04 The Agile Manifesto represents a shift away 1:09 from the generation of formal documents like a software specification. 1:11 A software specification is a fixed document 1:16 where the design of the product is determined upfront. 1:20 In contrast, the Agile Manifesto values the use of working software 1:23 to communicate the value being delivered. 1:28 We'll take a deeper look at how this is done in a later stage. 1:31 Third, the Agile Manifesto calls for 1:35 valuing customer collaboration over contract negotiation. 1:37 In the enterprise world, many companies work for a client. 1:42 The Agile Manifesto proposes that clients move into a collaborative role 1:45 with the teams developing software. 1:50 In this shift, the customer or team member representing the customer, 1:52 is part of the ongoing process of creating a solution, 1:56 rather than just being consulted at the beginning and end of the project. 2:00 Finally, the Agile Manifesto emphasizes responding to change 2:04 over following a plan. 2:08 It's more important to develop the right product than to stick to a plan. 2:10 As priorities change, an Agile team is able to continue to develop and 2:14 deliver value to the organization and the customer. 2:18 These values of the Agile Manifesto are backed by a set of 12 Agile principles. 2:21 We won't go into detail on each of these principles. 2:27 So I encourage you to check out the link in the teacher's notes 2:30 to get a deeper understanding of the thinking behind the Agile Manifesto. 2:33
You need to sign up for Treehouse in order to download course files.Sign up