 Gwsoff tactics�ы pasta sgwisiol, bwysig eraill, gyda risg cyhoeddfa ffraith,tvน y queue i'r awr songg talus wahanol, a yrgyn i'r Lord sefydluwon ar ôl anghylchwyscyrgyfryde, ac yn rhan i yn dod i'rین ffordd h spiritot y mae yn Go Russellhael ym Volunteers. Mae'r hun cyhoraeth am y Gymwe Deillol. Aуд ydym mor hemugi fel ym 308, health guidance awr nesaf, umd hacerlo am 250,000 ysgr棒, 150 nôr f weight, 310, nesaf, nesaf, nesaf, nesaf, nesaf, nesaf, nesaf, nesaf. Over a huge range of organisations, enterprises, have a look at the website if you really want to know more about us. We do the tool, the tool is kind of the main product, but we do services as well. So I'm a coach with Riley, so I go around, we don't just want to sell a tool and help people that the tool is going to solve all their problems. We want to help organisations to be successful. So we provide coaching as well so that when they're using the tool, they're using it more successfully and then we try and be really active in the community as well. So that's why we're sponsoring this conference and we have a whole lot of stuff on the website. So lots of content on there, lots of community support. That's kind of the combination of the three things, the tool, the training and the community that we think are a really powerful combination. Because I've only got 10 minutes, I'm going to really focus in on this demo and I'm going to talk about what we're doing with Dean Lethingwell's Scaled Agile Framework and what we're calling Agile Portfolio Management. So this is really a kind of a new market. There aren't any other Agile Portfolio Management tools after we've got Portfolio Management tools that are trying to work with Agile, but what we think we're doing is taking Dean's Scaled Agile Framework and how he recommends doing Portfolio Management and Dean was involved with Riley from the start. So we've been working with him on this over the last 10 years. We've kind of been involved in getting this to where it is today. Putting this. I can't really read that, but essentially there's three layers of this and I'll kind of try and go through it. I'll try and give the quickest scale Agile Framework training ever. The other portfolio level, this covers the entire business, anything in the portfolio. And this is this is Apex, really big things. Things that are going to cross-releases. And we've got architectural Apex in there as well, because when we're talking enterprise scale, you do need to do intentional architecture at the architecture just in time. There's this portfolio allocation. So how are what our strategic goals? How are we investing for Apex? Those Apex then break down into the program backlog. So we're now getting down into the features. What are the features that are going to get that deliver those Apex? And there's this concept of the Agile release train. So at least every quarter we want to do a release of features. Ideally more frequently, but most organisations are not able to do continuous work. So we're looking at features. Features should fit in one of these quarterly releases, but they may be bigger than fitting in a normal strength. So features then break down into stories and that's where you're into your traditional Agile teams. So this is where we started, where most teams are and then we're working our way up and now have functionality from the top down. So this is a dashboard. This is the information that we want to generate because what we're trying to do with Agile portfolio management is get real-time visibility, real-time reporting of the data that the actual scrum teams, the Agile teams are putting in. So instead of a project manager, a program manager having to generate stuff in a PowerPoint slide, we can create a dashboard like this which shows the reality of what's actually happening. Then we can use that. So we're getting feedback and the same way that we value rapid feedback at the team level, we want the same sort of rapid feedback at the portfolio level. So the things we have here, we have a Kanban board. So this is showing the features. Features have a workflow, so they just get created, they don't have an entry. Then they go through a proposal stage and this is just a sample. This workflow can be configured, but somebody will put some effort into put a proposal for a feature. If that proposal gets accepted, then we go into some more discovery work. Probably going off and talking to customers, finding out what actual details we need to build. Then we go into developing it. Once it's developing and employed, we want to go to a validation stage. We want to check is the thing where you built the right thing. This shows which features in a nice Cardwell style are in progress with some other information. You can see that once we go into development, at 56, we've got some progress indicators. So we can work out the progress of a feature based on its user stories, how many user stories have not started, how many user stories are in progress, how many user stories have done. And now we can either do that on account of user stories or we can do a sum, a roll-up of the estimates of user stories. That's our first visualisation, just looking at the Kanban board, seeing what work is in progress, what's safe to work with. Then we've got some little reports here. The active epics. So epics, those things are the portfolio level. Which ones are being worked on? And we can see this four here. This one's already completed. This one's about 50% burn, this one's 6% burn again. So we can start looking in progress and we have the investment category here. So in this demo environment, we're using Jeffrey Moore's investment categories of optimise, neutralise, differentiate. Optimise stuff that we're currently building now, customers are using and we just want to make it better. Neutralise is something where, there's the competitors out there that's got something that we don't and we want to neutralise that complexity. That or differentiate, there's just something for us. Rally portfolio manager is a differentiating investment. We invested in this to differentiate ourselves. So we can look at the epics and again these on track to these look healthy. There's some little algorithms behind here because we can put some anticipated, some plans start and end dates in. If we're getting towards when we plan to end it and we haven't started it, that's probably going to be a red flag. We can put some simple calculations in there. One question. Yeah? Portfolio management in this sense is the same as managing programmes or projects as a portfolio? Yes, so the portfolio is all your programmes and then your programme will break down into what we've made up of features, features that are delivered by agile teams. Yeah. Now, epics are the first two features. So epics are things that are delivered at the portfolio level. So let me just kind of scroll through. So epics are these things here. Epics and your portfolio. Epic backlog is your whole portfolio of really big things. So deans you. How epics can also mean what are the stories you've heard about? Yeah, so this is deans using epics and this is how deans using the word epic is. Diagram. I want to understand the larger uses. Because on a project level we understand uses what we may refer to a feature of a product which we develop. On a portfolio level we may talk about multiple effects. Yeah. A scaling across programmes. So what we found is that every organisation has its own terminology. Deans picked on. We can, you can configure. You can have as many levels of these as you like and you can call them what you like. So epics basically is a user story on a portfolio level? Yes. Very basic. Yeah, very simple. Yeah. It's something that's going to take months, maybe years to do. Really is really epic. So we got epics that are in progress and this is our epics that have not started and what you've come to see here is this is showing the plan style date. So we can give some idea and we can sort this so we can see which were the ones that we think we're going to be starting on next. Yeah. Can we get a similar view at the team level? Yes. Yes, so teams. I'm kind of focusing on portfolio but when we get down to teams, teams can have their own Kanban boards as well which show user stories if I workflow by user story. And then once I've gone through this I'll show you how you can drill down from an epic to features to user stories and then user stories. So if you do decompose user stories iteratively you can do that as well. Okay. I mean I actually meant to ask maybe part of my accent that I didn't pronounce it well. Team in the sense of logical group of user stories or a group of user groups. Yes, you can. So one you can group by your investment category. So what some organisers do is they have an extra layer in here that's just that grouping for you. So rally we have an initiative layer. So you've got an epic. So actually your initiative is your top layer and your epic. So yeah because you can have multiple layers in here you can have that's because we found some organisations, huge ones had five or six layers in that portfolio because that's how they did that sort of group. I mean one week of slice and dice the backlog is look at some of this cross cutting concerns like performance or you know turns out. Okay grouping. So we have so there's a couple of ways we can you can define custom fields on these things with a drop down if it's a finite set and then you do reporting on that grouping by that filtering by that or we have just basic tagging functionality. So you can just use tags. So you've got nearly the right to say you one would be able to view the progress based on the speech groups. Yeah, yeah and yeah exactly you're going to everybody's going to have their own personal preferred view of subsets of that and the others various ways you can do that. It's not like hardware for just no no no nearly everything in here is configurable. There are applets and then again features we can see which features are in progress with data, center information and then so this is actually grouped by so this is PSI 2 I think. So this is a potentially shippable increment. So this is a release train. This is something kind of three months worth of work. Again we've grouped it by that all the features that we think can go into this release and then this back level of work that's been PSI 3 so again that's that's that's one way of grouping things. Pretty much all of this stuff you can you can customise as a query language behind it. So either worth thing noting here you can't really see it. This column here is slightly shaded because you can see we have a weapon in a six here and we've we've got seven things in there. It's just giving us a warning that we've exceeded our weapons on that. And then at the bottom so this is the investment allocation. So what we've said is that this kind of demo scenario we want to equally invest a third of our budget into optimise, neutralise, differentiate. Differentiate, optimise, neutralise. That's what we want to be doing. This is what we've got in the plan. So this is what we've planned in and you can see that this is very different from that. So we can see that what we've done is we've planned a whole load of differentiate stuff in there. We haven't planned any. So that's feedback to us that our current portfolio of work that we're working on doesn't matter what we want to be doing. And then you can see what you're actually doing. So as Mark gets work gets done at the moment there's nothing completed here. This will get filled out. So again you can be constantly checking in. What's planned, what have we done and how does that match on to what our strategic plan is. So very much strategic. So what we're trying to do here is we talk about linking strategy to execution. Portfolio level is very strategic focused. Down at the team level it's execution focused and we're trying to put a link between the two so you can check whether your execution is actually delivering to your strategy. And then the last thing on here is this timeline view. With these portfolio items these epochs and these features you can put a plan start and end date. So when you think it's going to start and end and that's you know finger in the air but what this is showing here so this hatched line here is our plan start and end date. This is when we've actually started so it's looked at all the user stories under a feature and it said the first user story that a team planned into a sprint and started working on was started here. This is just based on real data based on what the scrum teams are doing and we can see that we now we've started later than we thought we were going to see. And then we've got a little progress indicator and that might say well that's at the moment showing 50% complete. So well we started it late but look when we were going to finish here and we're already 50% complete. So it's not a problem. Yeah. So there's quite a lot of stuff. No. This one's not interactive. This one is so this one here but I didn't give a one that the Wi-Fi is bad which is not good when you're trying to get a solution. It's back up again. Okay let's see. That's where I loaded all the so okay yes so I can expand this one out and I can say okay underneath that so this is actually a theme at the top this is even higher than the epic for that theme what are my epics what's the progress of those epics this is epic 21 I can expand that one down so yeah you can play around with this and interact with it absolutely so this is this this is just going to quickly show you the hierarchy so at the moment we've got these two themes here this top level of our portfolio and I can in the same way on that timeline it's going to work yeah I can start drilling down these and expanding them out and this should show that I go down for the story level so this is a theme that's an epic I know you can't read this that's the feature and then we're down into user stories here and you can see the difference here because here you've got at the portfolio item level you've got this nice simple cent complete but it's calculating once we get down to user stories you've got slightly more traditional is it just planned in progress completed accept it so you're more traditional kind of scrum schedule sense and we could keep drilling down and then this one just the same thing but it just stops at the story level so development teams might be more interested in that sort of drill down so I'm kind of out of time what I've not shown you then is that once you get down to the stories you're into traditional agile territory of having team backlogs team scheduling work into sprints getting them done marking them done lots of the usual team dashboard like burndowns things like that any other questions capturing more details around with the these portfolio items and user stories it is like a but a visual focus of various of various I guess visualise from a more scrum perspective that we have a we have a way to do these the state code you know the posting nodes yeah so you can get a a come down bold view at the team level yeah you can do that and then again you can define your own workflow each team gets its own view of its data there's a whole load I mean I've kind of just scratched the surface here once you're getting down at the team level there's a whole load of extra data you can put in there you can have your acceptance criteria you can associate tests and test suites with user stories so when tests fail the user story gets marked you can mark user stories as blocked and again that will ripple up as a report so you have it down on your dashboard easily see blocked work so where do you want to go and help teams because mostly I have seen and that we all the charts get generated yeah but typically you know the work and progress and stuffs like that but we don't have a diagrammatical representation we get more from a a tabular column level the load but not on a diagrammatical basis okay so here's a yeah the wi-fi is working here so here's a kind of a more team-based dashboard again you can see all the block to work here so program manager scrum master and I have that sort of view just kind of a summary for the release burn downs I wonder if I can find a team camp on board so this is showing for agile team one they came up with an original name again they've defined their own kind of fairly complicated workplace space and yeah these are all their user stories but they're they've been prioritized it's probably stuff that they've they've sprint backlog ready for dev dev and visualisation this is blocked if something's if I want to mark something as ready so I can say that might be a different way of saying this I've finished development on it so yeah that's a this is a more visual way of looking at it and we're actually moving in this direction moving more towards this card view base so even I don't think I've got it set up on here we have our iteration planning board which again is all just dragging cards into across into iterations rather than the list view it is probably going off in the middle yeah so I was looking for this because he has come asked us to typically handle a work of you know handling all the posted nodes on the white board yeah and we can't help the rest that's a external maintenance work apart from what we enter the data now right so we do things twice you've got better duplication there but that keeps the spirit on because people basically see the flow but still data needs to go on I was thinking if they would have any data like this yeah this makes it a lot easier to update in the tool if you're doing it physically dragging stuff on there yeah I mean this is yeah this is drag and drop I can pull that over there and actually we have a even newer version of this that hasn't made it onto the demo environment and yeah it's just kind of pre-released within so even I can get at it in our with our logins but nobody else can yet which has all inline editing and even it's even nicer than this oh you're trying to we're trying to really kind of up the ante on the usability so that's that should be available to the public weeks months yeah it's not really my job to say that sort of thing but it's going through just final testing and tweaking and maybe maybe this quarter is that safe if it doesn't don't blame me it's that's not a product or that's not a promise yeah I say Steve can say that we don't have like fixed release release dates or stuff we release it continuously so we just have to open final testing yeah so we do weekly releases and then we have a kind of a it's not quite continuous deployment but when we release stuff we then turn it on subscription by subscription so the first subscription gets turned on is for rally employees and then we'll kind of slowly roll it out so that gives us some some better testing some gradual testing there's a problem we can roll it back or fix it or just turn it off again so it's kind of featured toggle type technology yeah you can either so the iteration is is an object in itself you can add notes to that so sometimes we'll then actually have a that on that dashboard or they'll just have a little panel which shows the retrospective notes for the last retrospective so it's going to be visible every URL is unique so you can email a URL that's um as a you know if you want to just send the retrospective part um understand what is happening well what we'll probably do there is we have an API so you can expose reports outside of rally and it's you just create a read-only user that log in to rally pulls the data out and then you can embed that in a wiki or SharePoint so that's typically what we'll do with that sort of thing or do you have reports do you have reports within the I mean pretty much yeah yeah there's a whole load of um so there's there's two kind of ways of doing that one we have some standard built-in reports which are things like burn release burn down spin burn down as cumulative flow but then there's a whole lot of apps so we've kind of gone down the app routes but you can create your own custom pages and embed any old apps and whatever's in the catalogue yeah so some of the reports again we'll kind of roll slowly rolling this feature out you can you can either print directly from there or you can save it as a jpeg and then you could email the jpeg yeah so that's the other way all some of this stuff you can export to excel and then generate stuff in excel if you want yeah we can give you a trial yeah contact so I think you can sign up for a trial just from the website is that right yeah oh community edition yeah community edition is the free version yeah that's probably worth we have a we have a kind of a how would you describe a kind of scaling set of products from the community edition which is free but limited functionality so you know this is the top end you get everything so but you could start with a free one if you just want to play around with it yeah so we can set you over the trial subscription and after trial subscription if you choose to buy you just extend it so you don't have to start from scratch again so we yeah so in and in a trial we want to get you using it for real oh you know we'd come and we'd give you some training and coaching and whatever help we need free version is great for real simple yeah yeah yeah the free version is really just targeted a single small thing all right thank you