Summary
Notes
Transcript
I need to go for the kickoff.
The kickoff day is tomorrow. Hejsan eha. umI have Mequal, Ed's just called Brooke and I'm not too sure where George is, but I'll go ahead and brief you guys. So we have the kickoff meeting tomorrow This is the deck so far. We've repurposed some of the stuff that George went through. So we'll probably skip over the horizontal team and the scope because we just did it in that session today. Ed is going to take slide five, six and seven, just explaining, you know, the approach, the success.
I will take slide eight. nine, ten and eleven. And then discovery each one of you and I think what we haven't done yet with the client that I think would be really valuable in kickoff is to explain exactly more about the deliverables that they're getting and what it's going to look like. So I've obviously summarised the discovery here but each one of you should probably have your own slide so Suneha you should explain what it is you're working on and what they're going to get by the end of discovery and then we're going to get by the end of the design system.
And if you want to share your screen at this point, do five minutes and share anything to do with Figma if you think it's relevant, you can do. And then Mequal, it would be great if you could take the component mapping and content order. Again, if you wanted to share the Excel that we have and just to show them what we're doing. Now, this one's really important because you... because it's still a bit up in the air about the components. We don't want to promise to them that by the end of discovery that every single component is mapped out.
So what we'll word that we're going to do all the high level, but for some reason, if we're still working on it, it just goes into the sprints like the design system. Do you know what I mean?
So, uh...
Sorry, Mike.
And then.
So in terms of sharing my screen right now, would it work if I show them like if I put in like some screenshots in here? Because I was Okay, okay.
Whatever you think would be helpful.
Because it's a kick off, we want to kick off to the client and say this is what we're going to be doing in discovery, how it's going to run and what meetings you're going to be having.
Okay, yeah, yeah, okay, got it.
But what we haven't yet done is we haven't, we've explained to them the deliverables on Confluence, but it might be nice just doing a bit of like an interactive either walkthrough or screenshots just to show them ahead of time what they might see. And what I'll do is actually what makes more sense is I'll move the sessions.
Actually, what do you guys think? Do you think we should explain the deliverables and then explain the sessions or the other way around? Okay, so I will...
Oh.
No, I think we should explain the sessions and then the deliverables, right? Okay.
I'll Basically move the.
I'll move the sessions in.
Yeah.
What I'll do is I'll kick off, but I won't go deep diving into the sessions. What I'll do is I'll hand over to each one of you. So then you would cover what you're going to be covering in design as well as the session. You would do the same for tech and Ed can do the same for business. So if you want to add in screenshots, whatever you think would be helpful would be amazing. Mikko, if you want to add in screenshots, I'll share your screen, sharing your screens out there.
absolutely fine as well and then we get Varun if Varun is not available and he's not been briefed can you take this slide as well so you could share your screen on the solution design document if you want you can just explain that the pro I know we've not got a prototype to us to put together unless you want to bash out Claude put me together you could do something Most probably I'll just show them all of your conference page something from a diagram, something.
We'll show them the solution design docs. We do have that as a template and just say that this is the output that we're doing and then I will take the gap analysis and go forward And then Yeah, that's basically it.
This sounds good.
So I mean, I'm expecting like a five minute each department, so like Should I spend five minutes or more than five minutes on design? Okay, okay.
Does that make sense? Or do you think there's anything else important to kick off for the client? Call. We've got a whole hour, so I think each person should take five to ten minutes.
All right. Okay. I'm just going to go through and reiterate it with Ed as well. So no, it's absolutely fine. So Ed, basically, we're going to skip over team and scope. You're going to kick us off with these slides of just explaining the approach and KPIs. I will then do ways of working and our principles. George isn't here, but I'll ask him if he wants to take principles because he delivered it quite well. I will take the migration timeline and how discovery runs.
Basically, each session is going to then begin at giving over. So we're going to basically do what I'm going to do a high level of view of these sessions that me and Brooke The sessions.
I haven't updated. Oh, I just. OK, sorry. So basically, I'll just do a high level that these are the sessions upcoming and I'll be handing over to the team shortly so they can give you an update of what to expect. So Suneha will go first and basically update. She'll do some screenshots of the design system. She'll explain what she's doing, what they're going to get, what she's done so far and her design immersion.
He's going to take the component mapping, he's going to share his screen and look at the template and how it works, do a bit of interactive flow.
Also, Meg, Meg, Meg, so there is-I saw the design immersion session is on 8th of June.
Okay, so you'll do it. So you're going to take the solution design, share the document, display the prototype, and then I can take the go forward. Are you sure?
It's 12. Sorry, yeah, it's 12.
I'll be updating these.
Um... And so just to run through again so everyone is on the same page, I will kick off and explain that we're skipping the team and the Skype but if there's anyone new in the meeting that we didn't meet yesterday let me know and we can introduce. I'll then hand over to Ed, then Ed will hand back over to me, then I will hand over back to Suneha, then to Mikko, then to me, then to Ed. And we'll give George the opportunity to do the principles.
Should I put some minutes against it? Because I feel like it gives a good impression that we are on time in our delivery team time with our meet schedules. Yeah. So it's one hour?
she's not is she super important or no it's fine it's just uh uh just turn up with questions yeah don't prepare api exercises okay don't prepare any kind of like any other things yeah okay so it's her agenda mel's gonna run through one uh piece and then larissa will run through another piece they've both got business strategy and overall digital strategy so when we're talking about the emerging sessions anyone who's got one just say that they're collaborative exercises where we're coming prepared with that we need answering.
There'll probably be a few walkthroughs that you guys already aware and preparing and just explain that if you haven't already seen, we can send out the pre-reading. Um... And then so all we're asking people to do from a slide point of view is add to do your KPIs and your. approach bit by the end of today. So you've got three slides, five, six and seven. five six and seven oh yeah ah yes fine um me equal if you can do your slides which is 18 and 17 and 18.
so neha yours is 16 and if you have time at the end of the end of the day to make a bit of pretty pretty prettier feel free if a worst case you can it's fine and then i will update the dates And I will put on the times for everyone now. um is everyone else um um normally i'm in abu dhabi on a wednesday i can be here in the morning and go in the afternoon for another project in the afternoon whatever it is i know you've got a lot on with abu dhabi so um we're all going to be if we want to do it i've got them coming up with pratika as to how we're running uh tomorrow and what we need to arrange because it is only a one hour meeting so i don't want to put you guys out if we need to do it remote i think it's also fine i'll check with roman if i need to be remote So you're okay for the business meeting.
For the tech meeting on Thursday then, let's just assume it's the same as the business. We come prepared for questions. We ask what we need to do for the onboarding. Now remember, we put in extra ones for tech. So this is the onboarding one. You've still got another two hours next week for tech. And don't forget for business. Business, it was supposed to be longer, but they wanted it to be shorter.
That's fine. We'll just do a follow-up thing. And then content or CMS and all. and stuff. So is Baron on that? Because he's got time off and stuff. When's the content one?
So content one's next week.
So we've got two content ones. We've got one next Tuesday and one next Thursday. Then we've got another technical one on Wednesday and we've got a design one on Friday. So every day next week, but Monday, we've got a two-hour session. Yeah, every week. Yeah, every morning, basically.
Yeah. Okay, cool. So we, I think we need to click through and make sure that we've got full access to everything. Like I could find analysts yesterday, they were starting to freak me out because they said we've given it to them and all that sort of stuff. for the watch. There's a few other things. There's a few kind of weird things about Adobe that like you've got access to AEM and access to other things and like all sorts of stuff.
So I think we need to click around and really find some, maybe it's more of a thing. And he's already done it once. He's probably got a few more things, but maybe I'll ask him if he's right since I've got the The other thing I was thinking is, oh yes. I can go for two weeks. That's fine. Does George need to approve that or do I just say it?
No, I think just give your dates to Rima and it should be fine.
I'm going to book as well today. I'm just... You're coming? Yeah.
Because the problem was that... With my Manchester. You're all coming? Yeah. Cool. You're coming week two. Week two. It's way back week. Because the flight ticket has been, the flight has been fully booked. All right, cool. All right, nice. And then we'll do hotels after, right? Yeah. Okay, I'm going to set something up. Oh, we go. I want to run this by you. Maybe it's more of a thing, but like on component mapping, we're not gonna get every component, every kind of like, you know, like field and problem, but we probably just need the cadence of how are we solving components in terms of what legacy we're getting rid of, code, fields, otherwise. But we literally need to do that on a component-by-component basis. We should split that into sprints.
We should make it very clear that we're not delivering all of that by the end of discovery. We'll maybe just do one or two examples, and then we basically split the priorities. And obviously, we don't want to basically go into sprint six and say, oh, we should consolidate that with a component in sprint two. You know, like components that logically fit together. First take basic components and also we need to stick with them and say that, okay, this component has like a 15 piece. Do we really need that? We're getting rid of these four, you don't really need them. Or maybe these two fragments just in case.
Or if you need any extra field also, it's okay for us to add. Yeah, yeah, yeah. And those extra fields might help us to consolidate that into a single component. So it's just the principle and the cadence of that. And it's like, this is what we're gonna call it. So it's like, Like, We don't need to work out why every component's name, we don't need to work out why every component field is going to be.