Agile/Scrum Precepts

Quick reference

• 00:03 Hi this is Ray Sheen.
• 00:05 I'd like to take a few minutes to discuss some of the Agile/Scrum presets.
• 00:09 Understanding these presets will put the Agile/Scrum methodology into context.
• 00:14 We will start with a high level overview of some elements of Scrum.
• 00:19 As has been mentioned in other sessions,
• 00:21 Agile methodologies are built upon the principles of learning and then adapting
• 00:25 through an iterative approach,the use of collaborative multidisciplinary teams, and
• 00:30 a strong customer focus that responds to changing customer needs
• 00:33 through iterations and progressive elaboration.
• 00:37 Now Agile is one thing, but what about Scrum.
• 00:40 Scrum is the most popular of the Agile methodologies.
• 00:43 Approximately 8% of all Agile implementations use Scrum.
• 00:47 Although Scrum started in the area of software development, it's now being used
• 00:51 with a broad spectrum of projects that are implemented to change a business,
• 00:55 processes, or products.
• 00:57 Detractors of the approach claim that Agile Scrum is an undisciplined and
• 01:01 out-of-control project management.
• 01:03 They say this because it doesn't use some of the traditional project management
• 01:06 tools, such as Gant charts.
• 01:08 However, the process is very disciplined,
• 01:11 is a disciplined approach to accommodate flexibility.
• 01:14 It uses different tools than traditional project management, but
• 01:17 different tools does not mean undisciplined.
• 01:21 So let's look at some of the precepts.
• 01:23 I'll show a traditional project manager precept and the Agile Scrum precept.
• 01:27 This is not to say that one is right and the other is wrong.
• 01:30 Rather, it is to show that the methodologies are intentionally addressing
• 01:33 different types of projects.
• 01:36 First, traditional project management assumes customers know what they want.
• 01:40 They're able to provide a complete set of customer needs and requirements.
• 01:43 Agile Scrum assumes customers do not know what they want, the classic phrase,
• 01:48 I'll know it when I see it applies.
• 01:51 Another difference is the traditional project management
• 01:54 assumes that the future as it applies to the project can be accurately predicted.
• 01:58 Whereas the Agile Scrum methodology assumes that the future is inherently
• 02:02 unpredictable.
• 02:04 Traditional projects are based upon the precept that project teams and
• 02:08 team activities and processes can be clearly defined.
• 02:11 The Agile/Scrum methodology assumes that the project team and
• 02:14 processes will change often.
• 02:17 Traditional projects assume the communication Is improved and
• 02:20 clarified through documentation.
• 02:22 Therefore, there's a heavy emphasis on developing complete documentation.
• 02:26 In contrast, Agile/Scrum methodology assumes that documentation creates delays
• 02:31 and confusion.
• 02:32 There are delays waiting for the documentation to be created and verified,
• 02:36 and then confusion ensues.
• 02:37 There are two sources of confusion.
• 02:40 One is tied to delay.
• 02:41 By the time the documentation is released, it is out of date.
• 02:44 The other source of confusion is based upon the interpretation of
• 02:47 the information.
• 02:48 The same word can be interpreted differently by different individuals.
• 02:52 When relying on documentation, each person uses their definition.
• 02:56 When there is a discussion, these differences are often exposed.
• 02:59 Let me give you an example.
• 03:01 I was working with an organization recently that was doing a new product
• 03:03 development project.
• 03:05 A directive came out saying that teams would need to trim their product before it
• 03:08 would be ready for the market.
• 03:10 A marketing team member thought that meant changes to approve the appearance.
• 03:15 The engineering team member thought that meant to remove
• 03:18 features from the product and the manufacturing operations team member
• 03:21 through that meant to reduce material costs.
• 03:24 They all read the same directive, trim the the product, but
• 03:27 it meant very different things.
• 03:29 Another difference is the traditional projects track success and
• 03:32 failure of individual team members based upon individual performance.
• 03:36 The actual project outcome has little impact upon the assessments, whereas
• 03:40 Agile/Scrum assesses personal performance based upon the success of the team.
• 03:45 Most traditional projects assume the components of deliverables can be created
• 03:49 independently.
• 03:51 If the deliverables are specified properly when everything comes together it
• 03:54 will work.
• 03:55 The Agile/Scrum methodology assumes that components and
• 03:57 deliverables should be integrated with others as soon as possible.
• 04:01 This integration will expose hidden problems and
• 04:04 early integration provides more time to fix these problems.
• 04:07 Because of their experience, traditional projects rely on project managers and
• 04:11 subject matter experts to create accurate estimates of project activities
• 04:15 without regard to team input.
• 04:17 Agile/Scrum projects assume that team members background and
• 04:20 experience is different to the point that the estimates of project activity
• 04:24 are highly dependent upon the team members themselves.
• 04:27 Therefore, only the team members can make accurate estimates.
• 04:32 In traditional projects,
• 04:33 the size of the team does not make any difference to the performance of
• 04:36 the project, since every team member does their own thing according to the plan.
• 04:41 As long as they do their piece, everything will work out fine.
• 04:44 Agile/Scrum projects rely heavily on collaboration and therefore, small
• 04:48 teams are more efficient because they can reach a collaborative solution faster.
• 04:55 >> If the traditional precepts define your business environment,
• 04:58 then stick with traditional project management.
• 05:01 However, if the Agile/Scrum Precepts are a better description of
• 05:05 your business environment, then you should be using the Agile Scrum methodology.

Lesson notes are only available for subscribers.