AgilePM® Project Management - Introduction

Introduction to Agile 8 lectures 08:58 Introduction to Agile: Learning Objectives preview This module explains the background to Agile Project Management and presents an overview of different Agile approaches.It explains how Agile Project Management, based on DSDM, is positioned within different Agile approaches. It also gives you a chance to capture your concerns, if indeed you have any, about using an Agile approach.This module provides an introduction to Agile, an overview of different Agile approaches and where Agile Project Management, based on DSDM, is positioned within the different Agile approaches. Agile Project Management Source preview Agile project management thinking has been evolving over many years. DSDM stands for Dynamic Systems Development Method. DSDM is a robust Agile project management and delivery framework. It was launched in 1995 as an alternative to large prescriptive Project Management methods and has its roots in RAD which stands for Rapid Application Development. DSDM originally sought to provide some discipline to RAD. In 2007 the DSDM consortium released Atern. The word Atern was formed from shortening the words 'Arctic Tern', a bird that is seen as being highly collaborative. In 2011, 'The APM Group' and the DSDM consortium created the first accredited Agile Project Management Foundation and Practitioner qualifications. A common mistake made in project management is to blame a particular approach for the failings of one or more projects. The most likely cause of failure is that the approach has not been implemented appropriately.",DSDM has been a leading proven agile approach for many years and a subset of the full approach is used as the 'engine' for the Agile Project Management qualification for which you are studying. This qualification has been designed in collaboration with APM Group and the DSDM consortium. Agile Concerns and Issues It is likely that you have heard of Agile. There are many misconceptions as to what it means and how it is applied. These may be genuine but may also be based on hear-say or second hand experiences.These misconceptions may be because of misunderstandings about what agile is, or as sometimes happens, these can be lead by agile fanatics who insist that 'Agile does not do this' or 'Agile does not do that'. In reality, Agile has to be pragmatic and, in some organizations, has to be 'stronger'.Take a few moments to write down your concerns. You should find that they have been addressed by the end of the course. If you find they haven't then please contact us and our Agile Project Management experts will be happy to resolve them. Some common misconceptions and the Agile responses have been included within the support material for this module.Take a few minutes to note down any concerns you have regarding using an Agile approach to project management. When you are ready move on to the next lesson. What is Agile? Agile, in this context, is a generic style of working. It takes a holistic view of projects, rather than being just a set of delivery techniques. Have you ever been involved in a project that spanned several months only to have customers not use the end result? Most developers have and probably more than once. Assuring that what you develop actually addresses the needs of the client has always been one of the biggest challenges in any development. Addressing this problem was one of the motivations behind the Agile manifesto. The first guiding principle of the Agile manifesto states that 'Our highest priority is to satisfy the customer through early and continuous delivery of valuable outputs'.In a fast paced environment Agile ensures that solutions meet the business needs and is focussed on timely delivery. Delaying decisions as much as possible until they can be made based on facts and not on uncertain assumptions and predictions is fundamental to an agile approach. This does not mean that no planning should be involved – on the contrary, planning activities should be concentrated on the different options and adapting to the current situation, as well as clarifying confusing situations by establishing an environment where rapid action can be taken. Agile is all about flexibility, the principle of 'responding to change over following a plan' is considered a strength of agile. This does not mean that Agile does away with the need for planning. Things change, and you want to have flexibility to adjust and react to those changes. You clearly want to have a plan for where you're headed and approximately how you'll get there. But you also want to leave room to adjust your plan. You will see, as you move through this course, how the generic style of working is demonstrated throughout Agile Project Management.Managing an Agile project may require a different style of management compared to a traditional project. The generic core Agile elements underpin the Agile Project Management approach. Agile Approaches There are a number of specific agile approaches, as well as a generic agile style of working. Extreme Programming is a software development methodology, containing mainly programming practices such as Test Driven Development, Pair programming and Continuous Integration, but little management. Lean, which came from the manufacturing environment, is all about efficient processes. The focus is on eliminating waste from the production line and thereby reducing cost. Scrum is a very simple agile process, designed for delivering software in small chunks, taken from a backlog of work to be done. The strength of Scrum is that it is very simple. But this is also a weakness because there is no concept of a 'project' that is managing delivery of a finite piece of work, with a process containing a beginning, middle and end. Scrum, Lean and Extreme Programming are lightweight approaches with minimal structure and guidance. DSDM and Agile Unified process are stronger but are still agile. The strength of DSDM lies in it being designed to deliver projects in an agile way.As you have just seen, there are many different Agile approaches. Most agile methods provide little or no guidance on how to manage a project in an agile way, DSDM is the exception. Agile Manifesto In 2001 representatives of all the leading ‘agile’ methods got together in the USA and created the manifesto for the newly formed 'Agile Alliance' over a 2 day period.Some Agile methods, for example, XP are way over to the left hand side of the manifesto statements and others are seen as more 'middle of the road' . DSDM is more middle of the road but still conforms to the Agile Alliance.Agile has traditionally been seen as a way of delivering IT projects but it has been successfully applied to many types of project.DSDM fully embraces the Agile Alliance manifesto and you will see how this is demonstrated as you progress through the modules of this course. Which Agile Approach? 'Going agile' is not necessarily a simple choice, since agile is an umbrella term to describe a generic style of working. Within agile, some of the approaches are very lightweight and provide little structure or guidance. For a simple environment, these lightweight approaches may be sufficient. For a complex environment, where an organisation is running projects within programmes and where an organisation has to comply with formal processes such as CMMI, ITIL , or external quality processes, a 'stronger' agile approach is usually needed. Some organisations chose a lightweight approach, such as Scrum, and then build their own management structures around it. However, this complex corporate environment is just the backdrop that DSDM is built upon, often described as Agile with Rigor – it maintains agility, but is designed to work within and work with corporate constraints, many of which are non-negotiable.When choosing the right agile approach you must first consider the needs of the project and the corporate culture. DSDM is often described as Agile with rigour as it combines an Agile approach with enough control to suit most organisations requirements. Foundation Level - Module Test Foundation Level - Module Test Introduction to Agile: Module Summary This brings us to the end of this module. During this module you have seen how Agile has evolved over the years and that it is seen as a Generic style of working to ensure that the right solution is developed on time, within budget to meet the business needs. Agile Project Management is based on DSDM and it is this approach that forms the basis for the APMG Agile Project Management Foundation and Practitioner qualifications.You may still have some concerns about using Agile Project Management but these should be addressed as you progress through this course.This module has introduced Agile Project Management and explained where it sits with other Agile approaches. When making the decision to 'go Agile' the organisation needs to understand that this may require a change in corporate culture in order to obtain the full benefit from this approach.Additional Reading: Chapters 1 and 2 and familiarise yourself with the Structure of the Agile Project Management Handbook v2. Consider whether you have met the learning objectives and you can repeat any or all of the lessons. Review the support materials/resources, particularly - a) Agile Primer b) AgilePM White Paper c) Popular Misconceptions of Agile d) Integrating DSDM into a PRINCE2 environment e) Other Resources under resouces f) Attempt the module Foundation TestWhen you feel confident progress to the next module (Agile Project Management - The Basics). Introduction to Agile. 8 lectures 08:58 Introduction to Agile: Learning Objectives preview This module explains the background to Agile Project Management and presents an overview of different Agile approaches.It explains how Agile Project Management, based on DSDM, is positioned within different Agile approaches. It also gives you a chance to capture your concerns, if indeed you have any, about using an Agile approach.This module provides an introduction to Agile, an overview of different Agile approaches and where Agile Project Management, based on DSDM, is positioned within the different Agile approaches. Agile Project Management Source preview Agile project management thinking has been evolving over many years. DSDM stands for Dynamic Systems Development Method. DSDM is a robust Agile project management and delivery framework. It was launched in 1995 as an alternative to large prescriptive Project Management methods and has its roots in RAD which stands for Rapid Application Development. DSDM originally sought to provide some discipline to RAD. In 2007 the DSDM consortium released Atern. The word Atern was formed from shortening the words 'Arctic Tern', a bird that is seen as being highly collaborative. In 2011, 'The APM Group' and the DSDM consortium created the first accredited Agile Project Management Foundation and Practitioner qualifications. A common mistake made in project management is to blame a particular approach for the failings of one or more projects. The most likely cause of failure is that the approach has not been implemented appropriately.",DSDM has been a leading proven agile approach for many years and a subset of the full approach is used as the 'engine' for the Agile Project Management qualification for which you are studying. This qualification has been designed in collaboration with APM Group and the DSDM consortium. Agile Concerns and Issues It is likely that you have heard of Agile. There are many misconceptions as to what it means and how it is applied. These may be genuine but may also be based on hear-say or second hand experiences.These misconceptions may be because of misunderstandings about what agile is, or as sometimes happens, these can be lead by agile fanatics who insist that 'Agile does not do this' or 'Agile does not do that'. In reality, Agile has to be pragmatic and, in some organizations, has to be 'stronger'.Take a few moments to write down your concerns. You should find that they have been addressed by the end of the course. If you find they haven't then please contact us and our Agile Project Management experts will be happy to resolve them. Some common misconceptions and the Agile responses have been included within the support material for this module.Take a few minutes to note down any concerns you have regarding using an Agile approach to project management. When you are ready move on to the next lesson. What is Agile? Agile, in this context, is a generic style of working. It takes a holistic view of projects, rather than being just a set of delivery techniques. Have you ever been involved in a project that spanned several months only to have customers not use the end result? Most developers have and probably more than once. Assuring that what you develop actually addresses the needs of the client has always been one of the biggest challenges in any development. Addressing this problem was one of the motivations behind the Agile manifesto. The first guiding principle of the Agile manifesto states that 'Our highest priority is to satisfy the customer through early and continuous delivery of valuable outputs'.In a fast paced environment Agile ensures that solutions meet the business needs and is focussed on timely delivery. Delaying decisions as much as possible until they can be made based on facts and not on uncertain assumptions and predictions is fundamental to an agile approach. This does not mean that no planning should be involved – on the contrary, planning activities should be concentrated on the different options and adapting to the current situation, as well as clarifying confusing situations by establishing an environment where rapid action can be taken. Agile is all about flexibility, the principle of 'responding to change over following a plan' is considered a strength of agile. This does not mean that Agile does away with the need for planning. Things change, and you want to have flexibility to adjust and react to those changes. You clearly want to have a plan for where you're headed and approximately how you'll get there. But you also want to leave room to adjust your plan. You will see, as you move through this course, how the generic style of working is demonstrated throughout Agile Project Management.Managing an Agile project may require a different style of management compared to a traditional project. The generic core Agile elements underpin the Agile Project Management approach. Agile Approaches There are a number of specific agile approaches, as well as a generic agile style of working. Extreme Programming is a software development methodology, containing mainly programming practices such as Test Driven Development, Pair programming and Continuous Integration, but little management. Lean, which came from the manufacturing environment, is all about efficient processes. The focus is on eliminating waste from the production line and thereby reducing cost. Scrum is a very simple agile process, designed for delivering software in small chunks, taken from a backlog of work to be done. The strength of Scrum is that it is very simple. But this is also a weakness because there is no concept of a 'project' that is managing delivery of a finite piece of work, with a process containing a beginning, middle and end t accredited Agile Project Management Foundation...