An introduction to PRINCE2 Agile – webinar with Andrew Kell{"@context":"http://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.knowledgetrain.co.uk/"},{"@type":"ListItem","position":2,"name":"Project Management","item":"https://www.knowledgetrain.co.uk/project-management"},{"@type":"ListItem","position":3,"name":"Project management principles","item":"https://www.knowledgetrain.co.uk/project-management/project-management-principles"}]}

TranscriptRACI

Here’s the full transcript of the video. (Responsible, Accountable, Consulted, Informed) or

00:00:00 Sevcan YasaRASCI: Andrew, would you like to start now? Yeah OK, OK perfect. (with Sign-off) matrices are useful tools to clearly define roles and responsibilities for each task or decision in a project:

00:00:02 Andrew KellResponsible: Let’s make a start.: Who will do the task?

00:00:04 Sevcan YasaAccountable: So, thank you everyone for joining, just a quick start.: Who is ultimately responsible for task completion?

00:00:09 Sevcan YasaConsulted: I’m Sevcan and I’m the marketing executive at : Whom should be consulted?Knowledge TrainInformed. Knowledge Train is a training provider and owns AgileKRC which specifically focuses on agile.: Who else should be informed?

00:00:20 Sevcan YasaSign-off : Just before I head over to you Andrew, I would like to mention that at the end there will be a Q&A session. So, if you have any questions, you can always pop it down in the chat and Andrew will answer them at the end, Andrew over to you.(RASCI only): Who should sign off or approve?

00:00:34 Andrew KellStakeholder register: Thanks, Sevcan welcome everyone. Good afternoon, a couple of bits and pieces. It’s quite nice to see some familiar faces popping up in the participant list.A

00:00:45 Andrew Kellstakeholder register: Even people who’ve been on some of my courses have come back for more. Extraordinary. So welcome to the afternoon’s session just to explain how it’s going to work, and my plan is to talk for about 40 minutes or so and then we’ll have a Q&A session. And obviously, it’s an agile session, so we will finish on time at 5 o’clock or by 5. is a document that contains all key information about project stakeholders, such as contact information, level of influence, communication preferences and engagement strategy.

00:01:07 Andrew KellProject manager’s role: In terms of the Q&A session, if people think of questions during the session, please pop them in the chat if I think they’re relevant to address at the time, I’ll pick them up immediately.The role of a project manager is diverse and critical for project success.

00:01:16 Andrew KellKey responsibilities

: Agile is iterative and flexible, with an emphasis on collaboration, while traditional methods are linear and follow a planned approach.AgileHow do I handle scope creep in my projects? consists of a set of behaviours we’ll see what they are in a moment, yeah, I’ve just seen Hannahs comment in the chat.Define clear project boundaries, implement a change control process, and maintain regular communication and alignment with stakeholders.

00:24:16 Andrew KellWhat are some common project management challenges and how can I overcome them?: Yeah, this session is going to be recorded and eventually it will be posted on I think agileKRC’s or Knowledge Train’s website so there will be a recording of this at some point. I don’t think it’ll be immediate, but there will be a recording.Common challenges include resource constraints, unclear objectives, and poor communication. Overcome them through careful planning, stakeholder engagement, and a focus on continuous improvement.

00:24:29 Andrew KellInfographic: So, we’ll go through the behaviours in PRINCE2 Agile in a moment.Subscribe to our exclusive offers and promotions

00:24:32 Andrew Kell : There are also frameworks described in the manual. Not very many, and not in a lot of detail, and it does briefly mention some of the sort of Subscribe nowIT only frameworks, but very very briefly. And we’ll look at what frameworks it does talk about in a few minutes’ time, There are also five focus areas, which again, we’ll look at shortly.{"@context":"https://schema.org","@type":"ImageObject","contentUrl":"https://www.knowledgetrain.co.uk/training-courses/project-management-principles-infographic-v1.0.webp ","description":"Project management principles infographic ","license":"https://www.knowledgetrain.co.uk/license","acquireLicensePage":"https://www.knowledgetrain.co.uk/license","creditText":"Knowledge Train","uploadDate":"2024-10-18T09:00:53.000Z","copyrightNotice":"© 2024 Knowledge Train Limited. All rights reserved.","creator":{"@type":"Organization","name":"Knowledge Train","url":"https://www.knowledgetrain.co.uk"}}

00:24:55 Andrew Kell{"@context":"https://schema.org","@type":"ImageObject","contentUrl":"https://www.knowledgetrain.co.uk/training-courses/project-management-principles.webp","description":"Project management principles","license":"https://www.knowledgetrain.co.uk/license","acquireLicensePage":"https://www.knowledgetrain.co.uk/license","creditText":"Knowledge Train","uploadDate":"2024-10-18T09:00:53.000Z","copyrightNotice":"© 2024 Knowledge Train Limited. All rights reserved.","creator":{"@type":"Organization","name":"Knowledge Train","url":"https://www.knowledgetrain.co.uk"}}: There are techniques. Again, the techniques are not covered in an enormous amount of detail, but quite a lot of the well-known agile techniques are covered in the book, and we’ll touch on some of those later.Related articles

00:25:04 Andrew Kell : There are also a set of concepts, and again we’ll see what those are later on. So that’s what PRINCE2 Agile is.

00:25:12 Andrew Kell : So, let’s have a look at this thing called the hexagon and I know a lot of you in the group will be very familiar with the old sort of time, cost, quality, scope, triangle.

00:25:24 Andrew Kell : I’ve always been slightly confused that you can turn something that’s got four elements into a triangle, but it’s always shown as a triangle.

00:25:30 Andrew Kell : What PRINCE2 Agile has introduced and I and I really like this actually is the concept of a hexagon.

00:25:36 Andrew Kell : Where we’ve actually got six things to consider, so the hexagon has six elements.

00:25:42 Andrew Kell : It has time, cost, benefits, risk, quality criteria, and scope.

00:25:48 Andrew Kell : And what the hexagon says is that there are two of these that we should probably fix time and cost, and a lot of you will know that in agile there’s a very strong focus on trying to fix time and cost. But with the others there’s probably going to be a degree of variability, because what we can’t do on almost any project you ever work on is fix all of them.How to pass your Foundation-level exam in PRINCE2

00:26:09 Andrew Kell : You know you can’t fix time, cost, benefits, risk, quality criteria and scope.Simon Buehring

00:26:13 Andrew Kell25 Sep 2026: Unless you could run a project in a completely sterile environment where there was no change, no resourcing challenges, you know, completely accurate estimates, etc.

00:26:23 Andrew KellMaximise your chances of passing your Foundation-level exam in PRINCE2 with our targeted revision tips. Read on for effective study strategies.: So, and that’s not the real world, so we can’t do that.

00:26:26 Andrew Kell : So, we need to know in the real world where the wiggle room is.

00:26:30 Andrew Kell : You know where we have got some flex, so in agile we move towards the model where we try and fix time and cost.

00:26:37 Andrew Kell : You know we will fix elements of the other four, so there may be certain benefits that are fixed.

00:26:43 Andrew KellAI challenges in Agile project management with Dan Stelian Roman: There may be certain elements of risks that are fixed.

00:26:45 Andrew KellSevcan Yasa: There may be certain elements of scope that are fixed and in a lot of agile environments they talk about an MVP, which is non-negotiable, which has to be delivered.15 Sep 2026

00:26:54 Andrew Kell : Also, the quality criteria of what we deliver.Join Dan Stelian Roman in a webinar exploring the challenges of implementing AI in Agile projects. Watch to enhance your understanding of navigating these challenges.

00:26:57 Andrew Kell : You know we will fix certain elements of that, but we’re not going to try and fix everything, so we need to understand where the give is.

00:27:05 Andrew Kell : And again, this is this is very project specific, so for every project you need to look at this hexagon and say OK for each of these six areas.

00:27:13 Andrew Kell : What tolerance do I have? And those of you who are familiar with PRINCE2 will know that that PRINCE2 talks about tolerance, so we should define tolerance for these six areas, and ideally in an agile project time and cost would have zero tolerance.

00:27:29 Andrew Kell : And to come back to the PRINCE2 principle of managed by exception.The importance of a business case

00:27:32 Andrew Kell : Any prediction to exceed those tolerances would be described as an exception.Simon Buehring

00:27:37 Andrew Kell19 Feb 2026: So that’s the PRINCE2 Agile hexagonUnderstand why a business case is crucial for informed decision-making and effective resource allocation. Read on to master how to craft a powerful business case. I really like that.

00:27:41 Andrew Kell : So, what are the five targets?

00:27:44 Andrew Kell : I’ll explain the washing machine in a moment.

00:27:47 Andrew Kell : There are five targets defined by PRINCE2 be on time and hit deadlines again that’s a very key part of the whole agile mindset.

00:27:54 Andrew KellPRINCE2 Agile glossary: Protect the level of quality, first of all, understand what defines the level of quality and then protect it.

00:28:02 Andrew KellSimon Buehring: So don’t deliver things on time by cutting corners that you shouldn’t be cutting.19 Feb 2026

00:28:07 Andrew Kell : Third one is that we embrace change.Access a comprehensive glossary of terms from PRINCE2 Agile to enhance your understanding of its unique vocabulary. Essential for practitioners.

00:28:09 Andrew Kell : That’s a term you’ll find in across all sorts of agile approaches , so we don’t view change as a negative thing.

00:28:15 Andrew Kell : We know it’s going to happen.

00:28:16 Andrew Kell : When it happens, we’ll do something about it.PRINCE2 Agile behaviours

00:28:20 Andrew Kell : The 3rd, 4th one, once we’ve established a development team, try and keep that team as stable as possible.Simon Buehring

00:28:27 Andrew Kell19 Feb 2026: A common cause of project failure is chopping and changing resources during development. Of course, it is, its common sense, so as much as we can, we keep the team stable if we have to change the competition of a team do it at a sensible boundary. You know, do it maybe at the end of a stage or increment or release if you have to do it at the end of a sprint or a time box don’t do it midway through a development sprint of course that’s going to cause problems.

00:28:51 Andrew KellLearn about the five key behaviours in PRINCE2 Agile that can enhance agility in your projects. Scroll down to read more.: Finally, and this is where the washing machine comes in, we accept that customers don’t necessarily need everything they ask for, and the reason I put a picture of a washing machine on this side.

00:29:02 Andrew Kell : Sevcan was asking me about this yesterday and that’s quite a good example of a washing machine, I think because if you look at the front of it, there are so many buttons and options and dials and you’ve probably got you know, 10s if not hundreds of different washing options.

00:29:18 Andrew Kell : Most of us use two or three, and if we built a washing machine using an agile approach, we would build a washing machine that only had two or three settings because that’s what customers actually need, and it would probably be a much cheaper washing machine, and I must admit I’d buy it. I’d buy it in a flash.

00:29:36 Andrew Kell : There are all sorts of real world things that are just over engineered like that agile could fix some of those things car interfaces, coffee machines, those sorts of things in my experience. And maybe it’s just me that I can’t use them.

00:29:48 Andrew KellWhat is a Project Management Office (PMO)?: So, let’s have a look at PRINCE2 Agile’s behaviours and again there are five behavioursKnowledge Train in PRINCE2 Agile and we’re going to do.21 Aug 2026

00:29:57 Andrew Kell : We’re going to do a little poll on these in a moment.A Project Management Office (PMO) is a central function within an organisation that standardises project management processes, supports project delivery and ensures governance across project portfolios. Find out how PMOs add value, the roles they perform, and the benefits they deliver.

00:30:01 Andrew Kell : I’ll just go, I’ll just read them out for now and then we’ll do a little poll and then we’ll talk about a little bit more.

00:30:06 Andrew Kell : So, there are five behaviours defined by PRINCE2 Agile. The first is Transparency, again a word I’m sure a lot of you are familiar with, then you’ve got Collaboration, you’ve got rich communication, you’ve got Self-organization or what the latest version of the Scrum Guide called Self-Management. And then you’ve got Exploration.

00:30:24 Andrew Kell : Now I know that not all of you will necessarily know what all those words mean. We’re going to go through them in a moment, but I’d like to just do a quick poll with the people in the group. I’d like to find out which of those five behaviours .Tackling burnout: hidden drivers and sustainable solutions

00:30:35 Andrew Kell : You think is the most important for project success.Sevcan Yasa

00:30:40 Andrew Kell25 Sep 2026: So Sevcan if you’re there can we do that poll now.

00:30:47 Andrew KellExplore what really drives project burnout and learn sustainable ways to protect wellbeing, energy, and long‑term performance.: Oh, there we go.

00:30:50 Andrew Kell : Oh, there we go.

00:30:51 Andrew Kell : Look at that.

00:30:52 Andrew Kell: Well, this is very exciting.

: There’s also quite of information about Kanban, especially the Kanban method, which some you might be familiar with.Manage services

00:35:28 Andrew KellManage {vendor_count} vendors: It also talks about Lean Startup, which is where the original MVP term came from.

00:35:33 Andrew Kell: Some of the others are mentioned in passing, but there’s not a lot of information about those, but they are in the book.

00:35:42 Andrew Kell: Let’s look at the focus areas. So, there are five focus areas in agile.

00:35:47 Andrew Kell: First of all, there is this tool called the Agilometer.

00:35:52 Andrew Kell: I quite like that word because it sort of tells you what it does, and in the agilometer, which is basically the diagram on the top right-hand side of the slide.

00:36:01 Andrew Kell: There are six areas that you should look at and there are sliders that you basically apply to understand how suitable your project is for agile.

00:36:10 Andrew Kell: What it can also do is if you are going to use agile on your project, it can help you understand where some of the areas of risk might be, so are we going to struggle to communicate and work collaboratively.

00:36:21 Andrew Kell: Because we’ve got a global team that’s working in, you know, three different time zones for example, that you know is going to make it more difficult to do those two things.

00:36:29 Andrew Kell: So that’s something we should think about doing something about, you know, do we have wide acceptance of agile?

00:36:34 Andrew Kell: Do we have the right environment to use agile in? Are we going to be able to develop iteratively and deliver incrementally? And finally, is there flexibility on what we deliver to the customer?

00:36:45 Andrew Kell: If there’s no flexibility and everything has to be delivered at the same time, for example, then that’s almost certainly not suitable for an agile approach, so the agilometer is quite a nice little tool provided by PRINCE2 Agile, some of you in the group might be familiar with a similar tool known as the Project Approach Questionnaire, which is one of the other agile approaches which some of you might have come across.

00:37:09 Andrew Kell: Also, there’s a strong focus on requirements and making sure that we’ve got you know well defined requirements.

00:37:15 Andrew Kell: Again, in my role as an agile coach, I do work with lots of teams that struggle with requirements, and we’ll talk a little bit very briefly about user stories in a few minutes time.

00:37:26 Andrew Kell: Also, Rich communication actually comes up in two places in this, so it comes up again in the as a focus area. You know making sure that we’re using, you know, sensible channels for people to communicate with, and we’re trying to get away from those push channels like e-mail as much as we can and use perhaps more visual forms of communication.

00:37:44 Andrew Kell: Also, we try and release things frequently to the customer as frequently as makes sense.

00:37:51 Andrew Kell: You know, it might make sense to deliver something to the customer at the end of a sprint or a time box, or we might need a number of sprints or time boxes to actually release something to the customer.

00:38:00 Andrew Kell: But we try and make those as frequent as we can so that we’re frequently delivering value to the customer.

00:38:06 Andrew Kell: The final focus area is agile contracts and I’ve put at the bottom of the slide, I don’t know whether you guys can read the detail on that a little diagram that I extracted from the PRINCE2 Agile course I’ve worked on both sides of agile contracts as both the supplier and the customer, and I know how challenging they are because we can’t put detailed deliverables in the contract so you know and we and we shouldn’t have things like penalty clauses in an agile contract and that makes it very challenging, so that’s another one of PRINCE2 Agile focus areas, and it gives you some quite good guidance on putting together an agile contract.

00:38:41 Andrew Kell: What else have we got?

00:38:43 Andrew Kell: So, techniques and there are lots of techniques or practices that are considered to be agile.

00:38:50 Andrew Kell: I put together quite a long list of them on this slide, very widely used user stories which originally came from XP back in the 90s, used by most agile teams in my experience I always describe user stories as a simple difficult technique because the format is very straightforward.

00:39:09 Andrew Kell: It’s actually quite a challenge to write really good user stories in my experience.

00:39:13 Andrew Kell: It’s a real skill, Retrospectives and again, terminology I’m sure quite a few of you have come across before.

00:39:19 Andrew Kell: You know, frequently looking at how things are going, what’s going well, what’s going badly.

00:39:25 Andrew Kell: What might we do differently now that will make things better so very aligned with continuous improvement.

00:39:32 Andrew Kell: Then Burn charts you know most commonly burn down charts in my experience, but there are also Burn charts as a visual way of showing progress in a team. Daily standups or daily scrums both terms mean the same thing. For me a really powerful part of Agile, just an opportunity for the development team to have a just a quick, you know 15-minute quick catch up.

00:39:55 Andrew Kell: Where are we?

00:39:56 Andrew Kell: What issues have we got?

00:39:57 Andrew Kell: Are we are we on track? And again, my view as an AgilePM is if you come across the development team who are resistant to doing daily standup then something’s probably wrong. By the way, in my experience, again, in the real world it might not actually make sense to do them daily, but that’s a that’s a slightly different conversation.

00:40:16 Andrew Kell: Also, time boxing and doing work in fixed chunks of time, very agile behaviour.

00:40:22 Andrew Kell: You know most development teams would call those sprints because that’s what they called in scrum.

00:40:27 Andrew Kell: Measuring flow and this aligns very well with the sort of Kanban approach, you know, measuring our productivity as a team as we go through, and some of you may have come across things like cumulative flow diagrams and things like that as ways of measuring that.

00:40:42 Andrew Kell: Also, you know, a very collaborative technique, workshops or facilitated workshops they’re called sometimes.

00:40:48 Andrew Kell: You know, not rocket science if it’s helpful, get people together in a room to thrash something out.

00:40:54 Andrew Kell: That’s not a very scientific definition of a workshop, but that’s what they are basically.

00:40:58 Andrew Kell: Also, a very widely used technique and the PRINCE2 Agile Handbook Manual does mention this is a prioritization technique called MoSCoW.

00:41:07 Andrew Kell: It’s been around since 1994, I think was when it first appears been around for donkey’s years but a very widely used technique by all sorts of agile teams. Again, I’m just keeping an eye on the clock trying to get through these as quickly as I can.

00:41:22 Andrew Kell: So, what are the concepts in PRINCE2 Agile?

00:41:25 Andrew Kell: Well, first of all, always prioritising what you do?

00:41:29 Andrew Kell: And part of the agile mindset is to prioritise everything basically and ask the question, is this actually important?

00:41:35 Andrew Kell: And I think MoSCoW is a really nice way of doing that and some of you will know I’m an enormous fan of MoSCoW.

00:41:41 Andrew Kell: Delivering solutions incrementally rather than doing it at the end of the project.

00:41:46 Andrew Kell: As we discussed earlier, not necessarily delivering everything, and it’s absolutely key that the customer understands that you know as I say, on agile project management courses, the shiny stuff in agile is a really easy sell.

00:42:02 Andrew Kell: Telling them that they’re going to get everything they ask for is a much more complex conversation, but you have to have that conversation at the beginning of the project.

00:42:09 Andrew Kell: They’ve got to understand that’s effectively, that’s the compromise that they’ve got to accept.

00:42:13 Andrew Kell: If they want the shiny bits, also when we develop solutions doing it cyclically and iteratively, and getting lots of feedback as we do it.

00:42:22 Andrew Kell: I’m not, I’m sure some of you have heard the expression fail fast, that’s how we fail fast.

00:42:27 Andrew Kell: You know, getting things wrong, learning from that and then getting them right is actually a very positive behavior.

00:42:34 Andrew Kell: So, I’m sure some of you have come across what are sometimes called the pillars of agile.

00:42:38 Andrew Kell: Two of which are Inspect and adapt so frequently and regularly inspect how things are going. Adapt your behaviour to make things better.

00:42:47 Andrew Kell: You know fundamental cornerstones of agile. Also, being very time focused and having a very strong focus on finishing things on time, he says looking at the clock, also Limiting Work In Progress, and I know some of you might be familiar with Kanban boards where you might have, you know WIP limits Work In Progress limits at the top of each column, and that limits the amount of work that the team can look at any one time, and therefore they should only then take on new work if they’ve actually got capacity.

00:43:20 Andrew Kell: And that’s all about smoothing flow, which is fundamental concept of the Kanban method, which I’m sure some of you are familiar with.

00:43:27 Andrew Kell: And then finally, a word that’s often thrown around in agile is the word Kaizen, which, broadly it’s a Japanese word that broadly translates as changed for the better it’s not a direct translation, but it means continuous improvement, you know change things if they’re not working to make them better.

00:43:44 Andrew Kell: The final thing, I’m going to talk about and I’m almost on time is my concept and I’ll keep this very brief but I know so if you if you’ve been on one of my courses before, we’ll I’ve heard me talk about this agile by stealth means looking at agile as basically being common sense, and when you boil agile down to what it’s really all about a lot of it just seems really obvious.

00:44:06 Andrew Kell: Of course, you should deliver on time and of course you should calibrate with the customer.

00:44:09 Andrew Kell: Of course, you should do that makes complete sense.

00:44:11 Andrew Kell: Of course, you should deliver value early if you can.

00:44:14 Andrew Kell: The problem with agile or one of the problems with agile is all the jargon.

00:44:18 Andrew Kell: You know we talk about sprints and backlogs and time boxes and iterations and all the language that are floating around.

00:44:26 Andrew Kell: Do we need all that jargon?

00:44:28 Andrew Kell: Sometimes you don’t even have to call it agile, you know you could actually say, well, let’s just try this little technique. Let’s not go blazing in and say this is agile we’re doing things agile, let’s try and almost sneak it under the radar, hence the graphic, by the way, and isn’t an agile project, isn’t it just a project that happens to have some agile features at the end of the day.

00:44:49 Andrew Kell: This is a subject I could go on about for some time, by the way, but I’m keeping my eye on the clock and I know I don’t have time to do that, so that’s I think pretty much the end.

00:44:59 Andrew Kell: Just before we do the Q&A session, which we have still just about got time for just what else is going on at Knowledge Train and AgileKRC, I won’t read all these courses out for you, but you know we run courses in all sorts of different areas relating to the subject matter, Agile courses, Project Management courses, courses that bring the two together.

00:45:19 Andrew Kell: If you’re interested in following up on any of those, then either get in touch with me or contact Knowledge Train using the e-mail at the bottom of the slide.

00:45:28 Andrew Kell: Enough of the sales pitch that brings us to the end of the story.

00:45:34 Andrew Kell: Bit of a whistle stop tour, it’s very hard for me to talk about this stuff in a short space of time, as some of you will know from previous experience now it’s time for any questions.

00:45:45 Andrew Kell: We’ve got 13 minutes left just under that anyone has.

00:45:52 Andrew Kell: Carmine long time no see.

00:45:55 Andrew Kell: It’s a few years ago that you came on one of my courses, so I’m looking at Carmine’s question in the chat indeed. ‘Constantly trying to prove myself… yeah, PRINCE2, PMP, MOR, Agile DSDM done with me exactly kind of working in cyber security.’

00:46:09 Andrew Kell: Well, that’s an interesting one.

00:46:12 Andrew Kell: Oh, I know I give his answer all the time, don’t I?

00:46:15 Andrew Kell: But it sort of it depends on where you want to go, doesn’t it?

00:46:19 Andrew Kell: Agile Programme management would potentially be an option. SAFe might be another one.

00:46:27 Andrew Kell: I mean obviously I could mention PRINCE2 Agile.

00:46:29 Andrew Kell: You’ve got PRINCE2, so PRINCE2 Agile would be another one to look at.

00:46:33 Andrew Kell: I don’t know if you guys know this, but there is a three-day PRINCE2 Agile course and there’s a PRINCE2 Agile Practitioner qualification that you do at the end of it, so that’s another one to think about.

00:46:44 Andrew Kell: Other than that, I guess potentially SCRUM.

00:46:46 Andrew Kell: You know if you’re working with people who are using Scrum, then Scrum Master or something like that would be would be a good one to have.

00:46:53 Andrew Kell: That wasn’t a very helpful answer, was it?

00:46:58 Andrew Kell: It depends on where you want to go, basically, Carmine.

00:47:06 Andrew Kell: Right were there any, I’m just scrolling up the chat.

00:47:09 Andrew Kell: Were there any other questions that popped in the chat, have I missed any?

00:47:14 Andrew Kell: Well done to Chris for getting the cheese question right, by the way.

00:47:22 Andrew Kell: OK. So, Christian has just put a comment in the chat how can agile be used to manage a program with multiple projects running simultaneously?

00:47:31 Andrew Kell: OK. So first of all so PRINCE2 is obviously designed for running projects, individual projects. AgilePM is the same AgilePM which is based on DSDM which Carmine has just mentioned, is also based on running projects there is an Agile Programme Management handbook which does go up to that next, you know that container for multiple related projects.

00:47:53 Andrew Kell: I’m going to be honest with you Christian it’s challenging because in a program with multiple projects, you’ve very often got projects that are quite agile and projects that are not very agile.

00:48:04 Andrew Kell: You know, if you’ll again use a software example you’ve got, you know, building the infrastructure typically done in a more waterfall way, building the GUI, the front end, done in a more agile way.

00:48:15 Andrew Kell: No, there’s no easy answer to that question Christian it’s challenging.

00:48:19 Andrew Kell: It absolutely can be done, the two approaches that look at that are Agile Programme Management but there’s also SAFe.

00:48:26 Andrew Kell: I don’t know when you’re familiar with SAFe – Scaled Agile Framework for the enterprise.

00:48:31 Andrew Kell: Which, yes, if you’re in that space Christian, I feel your pain, it is a very strange space to be in, but it might be worth having something like SAFe. Potentially. Scaled Agile Framework for the enterprise.

00:48:43 Andrew Kell: That again takes it up to the programme and then the portfolio level actually.

00:48:48 Andrew Kell: Good, so I’ve got a bit cranky. Sorry, talking too much.

00:48:52 Andrew Kell: Are there any other questions from anybody in the group.

00:49:08 Andrew Kell: So, Emillia’s posted a question about the qualifications. So, there is yes, uh, nicely done Chris.

00:49:17 Andrew Kell: So there is a foundation level qualification PRINCE2 Agile and I did make a note of what the format was and then I’ve thrown the post it away that’s gone well. My recollection is that it’s 50 questions in an hour and it’s not a 50% pass mark. Sorry I was expecting this question so I wrote it down and then I’ve lost the post it that’s really stupid of me.

00:49:44 Andrew Kell: I know that the foundation one is an hour’s exam and I think it’s 50 questions and I think it’s a 60% pass mark or something like that. The practitioner one is a 2 1/2-hour exam. Also 50 questions I think it’s a 56% pass mark and it’s a scenario-based object. It’s a 60. Thank you Beina.

00:50:03 Andrew Kell: Thank you very much.

00:50:04 Andrew Kell: It’s a I think it’s a scenario-based exam.

00:50:08 Andrew Kell: If you’ve done PRINCE2 or AgilePM or MSP

00:50:12 Andrew Kell: The format of the exams is very similar actually to those, so there’s a foundation level, which is for most people generally pretty straightforward, and there’s a practitioner level which I would say is a quite challenging exam like they all are.

00:50:25 Andrew Kell: Sorry, that was a slightly vague answer hopefully that makes sense.

00:50:29 Andrew Kell: Who was it, was that. I’ve scrolled down too far, Emillia.

00:50:35 Andrew Kell: Oh, that’s a good question.

00:50:36 Andrew Kell: I’ve just seen a question from Chris.

00:50:39 Andrew Kell: I’m not the right person to answer that, but I believe that when you pay for the cost of the course, it includes the cost of the exam.

00:50:45 Andrew Kell: I’m 95% sure that’s true Sevcan, you might be able to confirm that if you’re there.

00:50:53 Sevcan Yasa: Yes, that should be the case.

00:50:54 Sevcan Yasa: What I am going to do is, uh, for both Emilia and Chris Dodds, I’m going to send them emails just about more information. Would that be OK for both of you?

00:51:02 Andrew Kell: Good idea.

00:51:07 Andrew Kell: Done, yeah.

00:51:08 Andrew Kell: Yeah, that would be a good idea to confirm that you got the others. Just to come back to Chris’s question any, any course that has an exam as part of the course of the exam fee generally, part of the course fee as far as I know, and I think is that have I missed any questions Sevcan, or have I got them all so very small chat box I’m looking at.

00:51:36 Sevcan Yasa: Yeah, it definitely is. I think that should be all, let’s just say.

00:51:43 Andrew Kell: In which case does that mean I’ve finished early?

00:51:50 Sevcan Yasa: Yep, OK.

00:51:51 Andrew Kell: So very unlike.

00:51:54 Andrew Kell: I could have spent more time talking through my slides in the end.

00:51:58 Andrew Kell: I don’t know if you’ve seen Carmine’s comment in the chat Sevcan.

00:52:00 Sevcan Yasa: Yes, I’m just writing her name down and which course are you interested in?

00:52:11 Sevcan Yasa: Agile, perfect OK.

00:52:14 Andrew Kell: Well, we can offer quite a few of those.

00:52:17 Andrew Kell: Yeah, and Chris has asked for the same thing.

00:52:18 Sevcan Yasa: Chris yeah, I’ve written Chris’s name down.

00:52:21 Andrew Kell: Programme yeah, so Agile Programme Management potentially for coming here, by the look of it.

00:52:31 Andrew Kell: Good so if there are any other questions, please put them in chat.

00:52:36 Andrew Kell: Otherwise, guys, I think we’re basically done.

00:52:39 Sevcan Yasa: Yep, I am quickly going to put a feedback poll, just so you can quickly answer 6 simple questions.

00:52:51 Sevcan Yasa: I would really appreciate it and I really hope everyone learned something new today and I can see that many people found it very interested, which I’m glad, and I’m sure Andrew’s glad about that.

00:53:02 Andrew Kell: This is terrifyingly immediate feedback Sevcan.

00:53:05 Sevcan Yasa: Oh, that’s impressive.

00:53:11 Andrew Kell: So far so good.

00:53:12 Sevcan Yasa: Yes.

00:53:15 Andrew Kell: Yeah, obviously this has been very much a whistle stop tour at a very high level There’s a lot more as some of you know, there’s a lot more I can say about a lot of these topics whether you want me to or not is a whole different question.

00:53:29 Andrew Kell: Thanks for the comments in the chat.

00:53:32 Andrew Kell: If anyone does have any questions, they think I might be able to address then, then please feel free to drop me an e-mail.

00:53:39 Andrew Kell: It’s [email protected]. I’m happy to deal with queries by e-mail. If they want to find out anything, more about anything we’ve talked about, et cetera. If it’s to do with courses, I’ll probably pass you on to someone at Knowledge Train or AgileKRC.

00:53:54 Andrew Kell: But if it’s to do with agile, yeah, please drop me.

00:53:58 Sevcan Yasa: I think Karen has a question for you, Andrew.

00:54:00 Andrew Kell: Yes, that one, so that’s a good one. So, we do talk about this actually, on the PRINCE2 Agile course and when we talk about closing a project, the final part of PRINCE2 in theory, closing a project down and doing that final retrospective and review should be a really straightforward thing, because as you’ve said in the chat Karen because you’re doing continuous improvement and you’re trying to improve things all the way through project there shouldn’t be any surprises at the end of an agile project, so closing an agile project down should be relatively straightforward.

00:54:36 Andrew Kell: You’ll have noticed I’ve just used the word ‘should’ about four times, so clearly in the real world that’s not always going to be the case, but in theory the lessons that you learn should be learned during the project.

00:54:48 Andrew Kell: Which again to me, has always felt like common sense.

00:54:51 Andrew Kell: You know, learning lessons at or after the end of a project is too late for that project.

00:54:56 Andrew Kell: Cheers, Carmine, speak to you soon, so that’s always been my view So you know you, you still need to close the project down and do that sort of project handover, but it should be very straightforward. Hopefully that makes sense Karen.

00:55:09 Andrew Kell: Yes, Thank you.

00:55:09 Andrew Kell: Sevcan just put my e-mail address in the chat Suzanne, I saw you asked what my address was. Sorry I probably read it out very quickly.

00:55:18 Andrew Kell: Cool, still got 3 minutes left if anyone’s got any other questions.

00:55:22 Andrew Kell: I can see we’re slowly starting to lose people.

00:55:26 Andrew Kell: I’m pleased that 27 have stayed for 57 minutes though That’s all, that’s encouraging.

00:55:37 Andrew Kell: It’s all gone quiet Sevcan.

00:55:39 Sevcan Yasa: Yes, I can see someone is typing, so yeah.

00:55:42 Andrew Kell: Oh OK, Oh yes.

00:55:44 Andrew Kell: Yes, I can see that.

00:55:50 Andrew Kell: Yes, just to pick up on Fiona’s comment this is the first one of these that I’ve done, I must admit.

00:55:54 Andrew Kell: But I’m hoping we will do more and I’ve actually got a list of my hobby topics that I’d like to talk about, us trainers love a platform to talk you know, we do.

00:56:04 Andrew Kell: So yes, hopefully they’ll be more absolutely right.

00:56:10 Andrew Kell: Thank you, Bina.

00:56:21 Andrew Kell: OK.

00:56:22 Andrew Kell: Thanks, Eduardo, thank you for attending.

00:56:29 Sevcan Yasa: I don’t think there’s going to be any more questions.

00:56:38 Andrew Kell: That’s almost likely.

00:56:39 Andrew Kell: Am I right of thinking that Olu you dialed in from Nigeria?

00:56:44 Andrew Kell: Sorry I’ve shortened your name to Olu that’s really rude actually I should just try and say your whole name.

00:56:53 Andrew Kell: I think I spotted earlier in the in the list of participants that you dialed in from Nigeria, so welcome.

00:57:01 Andrew Kell: Thank you, Karen, you’re welcome.

00:57:13 Andrew Kell: There we go.

00:57:16 Andrew Kell: Thank you, Emillia.

00:57:17 Andrew Kell: Thank you Modupe.

00:57:21 Andrew Kell: Yeah guys, you can drop off whenever.

00:57:24 Andrew Kell: Feel free to e-mail me if you think of any questions after the event.

00:57:39 Andrew Kell: Yeah, Alexa, I’m very fond of the expression agile by stealth and it genuinely will be the title of my book if I ever get around to writing it. Sadly, I’m probably a bit too lazy to actually write that book, but I know I should.

00:58:03 Andrew Kell: We’re down to 7, 6, Sevcan.

00:58:09 Sevcan Yasa: Yes, I think that should be the end those who stayed. Thank you.

00:58:16 Andrew Kell: Yes, thank you everyone.

00:58:18 Sevcan Yasa: Thanks, and have a nice evening everyone and to you of course Andrew. Thank you so much for everything.

00:58:23 Andrew Kell: No worries, cheers. Thank you for your support.

00:58:26 Sevcan Yasa: Thank you very much. Bye everyone.

00:58:29 Andrew Kell: See you next time.