Start at



Overall Course SummaryMany Projects and Organisations claim to follow an “Agile” methodology but on closer inspection are shown to do nothing of the sortThis one-day course aims toExplain what “AGILE” really means by reference to the ?Agile Manifesto in in which the core principles of the approach are set outExamine and dispel common misconceptions about what Agile is and isn’tProvide advice and guidance as to how to implement each of the 12 principles in an organisation or projectProvide examples of issues and pitfalls which might delay the full implementation of AgileReview whether partial implementation of some of the 12 Agile principles may still be of benefit or whether for some organisations or projects Agile processes are not suitable at allThe course is aimed at Senior Stakeholders and/or Senior IT managers who are either thinking of implementing Agile processes for the first time or are experiencing issues deriving the benefits they expected from their existing Agile processTimingLength (mins)Activity/Session outlineKey messagesMaterials08:3030Preparation TimeTo ensure rooms & materials are set up appropriately09:0030Attendees arrive and get settled in the training room09:3030Course Introduction and OverviewProvides an overview of the whole course.The course will begin by reviewing common misconceptions about the Agile Methodology and how this have led to the methodology being incorrectly applied by many organisations and projectsI will also explain that, to use a culinary analogy, the Agile Process must be viewed a fixed menu and not a buffet from which diners can pick or choose dishes as they see fitI will then ask participants to talk about “agile” projects they have been involved in and whether they were successful or not. As we move through the course we will access how closely the success or otherwise of these projects is related to how closely the details of the Agile Manifesto were followed.I will conclude by explaining that the remainder of the course will concentrate on understanding the detail of the original Agile Manifestoproviding insights into not just what it means but why the Manifesto includes exactly the set of items it doesand explaining how each principle works to support the others in promoting a mindset which helps consistently deliver valuable software to organisations which properly implement the processSlidesGroup Discussion10:0015What is Agile?This session explains how the Agile manifesto provides a means by which we can determine if a process is truly agile or notIt will introduce participants to the 4 Goals and 12 principles which make up the Manifesto and explain how these individual elements will be covered during the remainder of the course It will also try and debunk some of the most common misconceptions as to exactly what Agile and what it is notSlides10.1530The 4 GoalsThe Agile Manifesto contains 4 goals which exist to place the detail of its 12 principles into context This session looks at each of the 4 goals in detail explaining what the true purpose of each is and how each is designed to work together with the other Goals to deliver AgileMany attempts to introduce Agile fail because people have only partially understood or applied what is set out in the 4 Goals so this session will also highlight the most common misconceptions in this area 10.4515BreakAfter which our focus will turn to the detail of each of the 12 Principles which for convenience has been split into 5 groups 11.0030Our Highest Priority is to satisfy the customer (Principle 1)The most important principle of the 12 and perhaps the most commonly misunderstoodIn this session we will explore exactly what this principle means, why it is seen as the most important and try and understand why the second half of the principle often does not get the attention it deservesSlides 11.3030Continuous Delivery (Principles 3, 7 and 8)In this session we will discussExactly what is meant by continuous deliveryWhy this is seen as so important by the authors of the Agile ManifestoWays in which your project/organisation could move towards continuous deliverySlides12.0030Implementing A Process of Continuous Delivery – Issues and GuidelinesHaving explained what continuous delivery is and its crucial importance to the Agile Process this session willExamine some of the main issues organisations run into when attempting to move to a process of continuous delivery for the first timeDistinguish between issues which are within the powers of the delivery team to address and those which require a fundamental shift in approach to software delivery on the part of of the organisation as a wholeSlides12.3045Lunch13.1530Collaboration and Collocation (Principles 4 and 6)This session will explain how each of these 2 principles reinforces the other explainingWhy both are critical to delivering a truly agile processWhat generally happens if you try and implement “Agile” without either of these two principles being properly adhered toSlides13.4545Building an Environment in which Agile processes can flourish (Principles 5, 9, 11 and 12)The 12 principles are NOT a step by step guide which organisations can follow in order to deliver AgileThey aim instead to promote a mindset which helps organisations deliver high quality software.Agile processes will only flourish in an environment which has been designed to support and encourage them and this session will discuss how these 4 principles can assist in building such an environment. By the end of this session it will be clear that in almost every case, that for Agile processes to succeed it must be a change which is introduced across the organisation as a whole and not just within the IT department Slides14.3015Break14.4545Simplicity and Acceptance of Change (Principles 2 and 10)Responsiveness to change is perhaps Agile’s greatest selling point and this session will review how when properly implemented these principles will make an organisation better able to cope with change.It will also highlight that the failure of “Agile” organisations to deal well with change is almost always the result of either a failure to understand these principles or an unwillingness to implement them as the authors of the Agile Manifesto intendExercise: Introducing Simplicity15.3030Review of the Manifesto as a whole - Key Points to remember This session will emphasise the following key pointsAgile usually needs to be introduced across an entire organisation to be truly effectiveResponsibility for making key decisions needs to be devolved to the Agile teamA very different approach to project management and reporting is requiredThe session will include a structured discussion in which participants start to relate the 12 principles to aspects of their own daily workSlidesExercise: Applying Agile Principles in the Real World16.1545Wrap Up SessionThe course will conclude by providing participants with a series of different scenarios, asking themIs each project/organisation one to which Agile processes should be appliedIf so, what are the key issues that doing so is likely to involveSlidesAgile YES or NO exercise 17:00CLOSE ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download