Summary
Notes
Transcript
Hello. Hello. Smea, how are you? Smea. What is this? Australia project? Australia holiday?
Hello.
No, no, no. I'm better now. Better today. Not completely better, but I thought feeling little better, so I should join. I'm excited to work on this project. I'm coming back sooner than... I sure did. Australia holiday?
Mozilla got to make a Australia project.
Fair fair fair fair US fair fair fair US project.
Oh, it was a holiday on Monday. Yeah.
India You are the first Indian who is taking all the holidays benefit.
Yeah. I'm thinking that is a good strategy. he is laughingTrue, true.
Sorry to be late.
That is true. Hiya Kancha!
Mom, maintain. 12 minutes. Hi.
We were just discussing snails taking Australia's holiday.
My Hi.
Hello. Hello.
Time to go. I have not met.
Nice to meet you, Akanksha.
Yeah, nice to meet you. I'm not with it today. I just came. I just came from a Salesforce meeting. I just got to switch my brain back to Cycle for a minute.
laughs Yeah. Okay.
Give me.
Yeah, I think that's how it works. I think that's why horizontal's proposition is so important because it's tied in with the brain.
Okay, right. So for those new to the Basically, the way that we're running Stand Up is obviously reviewing our daily plans, so I am sharing it. So just from yesterday, Varun, you had two things on your list. Do you want to give us an update on how they went and your team update for today?
STD template and approach has been updated in Confluence. I have begun looking at information architecture because it is also part of the tech deck. I am ready with a foundational structure for all of us to really look at. But then I had a couple of questions we all will discuss. How do we want to run the tech immersion tomorrow? Based on that, how much detail do I add to the PPT and how much do we keep verbal is something between us to look at.
We can look at it at 16th minute after everybody's updates are completed.
Okay, so the actual tech debt for tomorrow, the prep that we're sharing, I've seen something on Mikko's desktop. I'm happy with what that is like literally nearly there for me I can share one thing Because I generally think, guys, that's enough prep that Brooke is expecting. Just whack that on the client channel and move on. Like, don't overthink it.
Let's connect. I have prepared a flow. If it's not worth it, I'll delete it. Don't worry. And we'll put what we have as a couple of slides. Okay.
You guys do what you need to do, but just don't overthink it, right? And we have said to the client to expect it soon. So ideally, it was supposed to be yesterday. So please, let's try and share it with them. Obviously, they're not awake right now. I guess if you don't share it to the end of the day, it's not the end of the world. But I just think if you get it out of the way sooner so we can just focus on something else, then that would be great.
The other thing I wanted to ask you about, Varun, is the key deliverables. Have you had a chance to work through my confluence?
Yes, I have already started updating them. If you look at the key deliverables, Sheet I have updated two things there.
Okay, perfect. I'll have a look. And do you have any blockers, Varun?
No bloggers as such. If Claude can get me maybe 48 hours more, I would love to take those.
You've created an IT ticket for that, right?
I have. I have updated the same ticket because Kevin had mentioned if you get an approval written from George, I'll make it max. So I've just updated the ticket. I am expected to get, I think Kevin is in the US, So probably by evening I should make it to the max plan.
Every single person on this call has approval to make it a match plan. So let's make sure that no one reports blockers throughout this project that they're blocked by UCIS. So that's just an FYI for everyone. All right, Varun, anything else?
Yeah, I would like to catch up with you one to one later. Mike after this call whenever you have time, please let me know.
Yep, that's fine. I will check my diary. It is crazy, but I will find time.
I know, I'm sure.
All right, I'll move on to Ed. Hello.
I need to refine Miro and I need to do slides on phasing, but that's for internal. Refine Miro is the more important thing and then the notes, I didn't do that KPIs. I'll do that. I'll do of those by the end of the day and then, sorry, refine Miro and KPIs by end of the day. Yes, on track, fine. Then all the thing, all deliver prep for a second content session is done. So basically because I kind of overdid it this time around.
So tomorrow will be a simpler day, which is good because I'll be at morale all day. and the notes as well you want to do notes so do you have a format you've done them I just need you to change and review them and then I'll send them end of day All right, cool. Review those, KPIs, and thingy. The other one, refineMetal. Yeah. You said you said you are going to be attending a call tomorrow.
Attending what? Tech call. Yeah, yeah, yeah.
And the TransPerfect one as well.
Yeah, yeah, yeah. That's fine. TransPerfect. Yeah, all that's fine. Me and Rohan just discussed our logistics in terms of me getting there.
Okay, okay. All right, I will move on to Suneha.
Hey, Mag.
So I have a bit of a delay on my side but I'm like on track with the plan that I have. I need to update it over here. So I'll just add those deliverables for the week in here. I am done like around 50%. On the elements, so foundations, the first layer is done. The second layer I'm done almost like 40 to 50%. And I plan to work through the entire elements layer this week. In terms of the deck that you've mentioned, are we running the immersion session on Figma or like?
So, so.
So the session doesn't have to have a structured deck or narrative or a flow.
Because I was thinking FigJam would be a good place to run it.
If it's an interactive session like Ed ran his on Miro, you can run yours on Figma. All I'm asking for is that the client gave us a bit of feedback that every session, if we can just go into the session just sharing a PDF, a deck that just reiterates the agenda that we gave them and saying that these are the types of sessions that we're going to be doing. questions that we're going to ask this is how it's going to run and then send it ahead of the meeting so they're prepared so that's all we're asking um it doesn't have to look super pretty um it's just it's just reiterating what we're going to do and that's the reason i said share it on wednesday because then the client's got a day and a half in case they want to make any changes OK, OK, perfect.
Okay.
Okay. Yeah. Yeah, I've already started prepping for it and working backwards. So I'll have that tomorrow. Yeah.
Meikle?
Currently tech immersion session. I just created a basic slide. Working on compound mapping, which is what Varun and I need to do.
The other thing is that I'm set up in a Sitecore solution with all components which we do demo for next week. Some part has been not working. Looking at.
Yeah.
I'm not sure. I think we discussed it. I was about to put that message and then there was a tech channel created. I will be tagging you as well and we'll put the message in that channel asking for if they have the Sitecore solution created. sorry, Sitecore license available for with the portal and everything for TA. Soundbox. Yeah, not sandbox for them. The environment. The complete environment.
Yeah.
I don't think that you need me to complicate things.
Tomorrow we'll ask it in the call itself.
Yeah, yeah. Fire it away into the tech channel.
What do you...
Mainly the license element.
If you are a white since.
There's no qualms. The signature on the license was meant to be the exact same day that they approved and signed our license.
Worst that can happen, they say, "Oh, we're still working on it. We need another week." There's no harm in just saying like, You know, like who's the owner of this in terms of setting up as a license there, the quicker they set up the better. Obviously, my only concern when you read this before was the setup of Sitecore as an instance, Data Weavers was very specific that there's a certain couple of things that you need to set up that helps them, that is basically required for them to be done.
So as long as we basically just do it with their input, then that's fine.
Yes, yes, yes. We will set that meeting up with them for next week. Again, for now, we'll be doing things on our sandbox for nothing to worry about. But then having that information will help because then if you want to set up SSO and other things, we can kick off pick them up and get to work. All right.
Do you want me to do anything?
No, no. I was just going to tag you. If all of us have a few minutes, I'll just take us through That slides real quick. Yeah. Yep.
I have a hard stop in a few minutes, but let the team carry on if I drop off.
Good, no problem at all. Again, tech immersion session. This is just more of an information that we'll need to focus on discovery really well. Then wanted to just put the purpose of this meeting or the session and roles, what both the teams will play and how everything should basically come together. Within our discussions, we'll try extracting from that. And basically the STD is going to be the proud design baseline forward solution. And then we want to discuss about 10 exact areas.
Although we want to focus on some right now and some over the next week. needs for detailing and our thought process is these four items is probably something that is going to flow in again integrations as well in the next week as more detailing KPIs and success criteria again, because it's a part of the agenda, I wanted to still cover it. But then I just want to say that Ed already covered this, but then just as a conclusion,The, uh...
Yeah, yeah, yeah. One of those is going to be dropped. Just take the numbers out. Just take the numbers out. That's the best thing. Wait. You've just copied the slides across, right? Yes, I did. I did.
I can remove these slides completely. I just wanted to keep-removing is better than adding them for data. So what I'll do is I'll remove these slides.
Yeah. Just remove or hide those ones, take the numbers away because they're going to basically think of feedback on the 35 or 34 or whatever KPIs and then it will be finalized. Let's not imply that we finalized already.
So I think the quicker that you get to that and the more time you spend on that, the better. So if you go through some area like template component library, Uh, you know, like encourage them to like, share their screen flip it around and they go like okay could you show us this now that's the point of them showing this this in advance so if it's nick going through these things he looks at this deck and he goes i'm being asked to look at i'm being asked to show basically what what how our technical setup is with templates and components and then all you're doing is we've noticed this we've noticed this we've noticed this is there anything else we should be talking about could you give us an example of how this works could you show us basically where you've got this set up or is there any document you want to walk us through that will help or this kind of thing.
My thought process was around architecture, localization, and authoring and governance, those three parameters to be focused on tomorrow. Integrations I will have to do in person. Thank you. Okay. Because whatever we can cover tomorrow, it's fine. Otherwise, next week we'll take it up. Yeah. Awesome. Yes, ma'am.
So it's more of a conclusion and confirmation that you want to ask that, hey, 83 components are in scope. It looks like 15 components have external API and secret management. There are 39 components which also have code plus a dialog drift. And tentatively, it was put up to 550 story points. This is on the same Excel file that we have. And then tentatively, this is the effort that it looks like. What are your thoughts?
I mean, I don't have the component discussion yet. Like that's not part of the immersion session. It's going to be like a large overview of like what is it that we want to keep from brand? What are the accessibility guidelines that do we already have something and do we want to like add something fresh? It's going to be around that. In terms of components, what I would be explaining to them is that if we build a component, then how are the variants laid out?
What is the responsive structure? What is the modes that you get within these components if they're built? So it's going to be mostly around that. This is not, I mean, in the design session, there's not going to be a component mapping talk.
We would like to focus on architecture, these three points first. If the discussions go on for further and we are unable to cover components then unfortunately we do to start there but if possible we'll cover this conclusion and you know as somebody will cover and then it can be a starting point for your design session all right OK.
So Ed and Mikul I will be sharing this. I'll put it on our SharePoint and then I'll share it on the internal channel for Okay. Okay. Thank you all.