and just so you both are aware the meeting is being recorded. Okay, I'll share and I think it'll automatically send send you the a copy of the transcript or a link to the recording. And I also have to remember to add it to the well I don't think we have a recordings channel. Oh, maybe we do I have to check into that. That's something I need to ask at our sprint planning.
Okay. Yeah, just so you know, for the sprint planning. There are saying in our leads chat that it should just be leads for tomorrow's sprint planning.
So Oh, for the first one, probably because there's still some leadership stuff to get through.
What are you thinking? Do you think that's a good? Do you think that's a good decision?
Well, um, if they mean only this time, because there because we're not able to do another ruminate leads meeting. If it's a one off, I think that's okay. Because there are probably some leadership decisions that still need to be made that require discussion. Okay, if they mean all the time, then no, I would disagree with that. And I would discuss that. Okay, but they just mean just once.
Yeah, seems like it's just this once.
Yeah, it's it is less, far less than ideal. But I think, you know, there may be some things that need to be discussed. I don't know. Okay, what are your thoughts?
I think yeah, just for this sprint. Planning tomorrow. It can't just be lead, but in the future, we should include everyone.
Absolutely. So yeah. And I'm sure that's what they mean. I can't imagine that they would think that we should be doing planning without all the teams and that is not that's not the way agile or like Scrum or any of that stuff works. You know what I mean? Right. Yeah, exactly. So yeah. Hopefully because they're not able to squeeze in a separate ruminate leads meeting prior to like the end. Of The Week. That's probably what's driving it. And it's probably I'm sure, it's just a one off but yeah, we'll we'll we'll make sure that we voice how we feel about it. If it's anything less than that. Anything more than that? I
mean, yeah. And then John sent a what do you call it a tentative agenda for tomorrow's meeting?
Oh, great. Okay. Sensitive agenda. Can you share it in the Oh, wait. Nevermind, I was gonna say in the chat, but since the first one is just going to be ruminate leads. Okay, I'll make a note so I go back and and review it just I'm sorry guys. I had to make a quick note.
No worries.
Work. I just need a minute.
Okay, certainly no problem, Angela.
Is there anything you want to highlight on that for us for the meeting tomorrow? Anything I need to know?
I think we need to really make clear what our role in this project is gonna be like, I have a feeling that design and they don't, they don't know.
talk with you about but we didn't have time because, you know, we had to we had to get through the candidates, which normally we'd already done all that. But you know, we're doing the best we can, right? Yeah. So what I want to do and we can and I can do it right after this meeting is I want to invite them let not like an actual meeting invite but I want to invite them to meet with us and I'm thinking like even a 30 minute meeting. Separately 30 minute meeting with design, UX and, and one with Dev.
Okay, so two separate events.
Yeah. So that we can we can, quote unquote, sit down together and talk about what we can do. Because we can tell them what we think we can give them or what we know we can give them and what we have planned or and how we want to work or think we can work well with them. And then they can give us their feedback on what they need.
Okay, yeah, yeah, cuz dev have Dev and design have been having meetings together. So yeah, we really need to like
yeah, and and we're we're just running behind right? But I've got you now. So, you know, and I've got a fairly clean, clean bill of health so to speak. You know what I mean?
Yeah, so you're gonna, you're gonna send a message or yes, just Yeah.
And if you could do me a favor if you don't see a message. Like, even if you say like at the end of this, like he needed don't forget to send that message.
Yeah, okay. All right. I'll make sure to remind you.
Yeah. And I say that just because I'm sleeping. Yeah. And, you know, you know how it is. Let's see. Yeah. 30 minute meeting. Yeah. Just tell them you know, just a 30 minute meeting to sit down and just have a chance to talk about our roles and you know, how we can work together. Um, and then also because we don't have the apprentices yet. We'll do we, you know, you and I can do our best to try to cover the, the meetings, you know, that they have to get to know their workflow and things like that. Because I don't know their works good. Do you know their meeting scheduled?
I just know that Dev and design have a meeting while Wednesday I want to say yeah,
enjoying that, you know,
I'm not able to join this one.
Okay. What time is that meeting?
3pm Eastern
3pm Eastern. Yeah, I can do that.
Yeah, if you could do that, then. Yeah,
I mean, even if I did it for like a half hour and then had to hop off so that they could ask me any questions and things like that at that. I'm saying like, on a regular I could do that. Yeah. And then when we get our Angela will and we'll ask him jolla about also covering. Yeah. Um, you know if she can, oh, you're back, right. Um, so Angela. Yes. And I'm just asking you, not necessarily this Wednesday, cuz I'm going to make an I'm going to go to this one. Myself. Definitely. Well, I'm going to ask if I can attend this meeting. When you put this way. It's between design and Dev. Okay. So to meet with them at they have a regular meeting at 3pm. So I was going to ask if I could attend that meeting. And you know, because normally we go to each other's meetings and then that way we can bring any issues, take issues back and brief. The others, you know, a members of our teams on on those meetings. So assuming that they agree. I don't know if that's a meeting that they want everyone in on so I have to do a lot of asking around that. But if they're in agreement is 3pm. Eastern, a time that you could regularly attend that meeting? If they would like someone from product to attend that meeting? So there's a bunch of hits in that.
Okay, so the meeting is weekly, right?
I don't, I'm not sure if it's weekly. I know it's for sure this Wednesday at three Eastern Standard Time.
Okay, so that's something that's TBD. Oh, yeah, that's so Angela. Keep that like in the back of your mind. It may not necessarily be solid every week. Okay. Were would you be able to attend that if they are open to someone from product regularly attending?
Um, Wednesdays 3pm. That would be 8pm. Yeah, yeah, I would.
Okay, so I'm making a note of it. And like I said, I have to follow up because there are several ifs in that. And, you know, I need to ask permission and, you know, find out whether it's a regular or not, but that's good to know that you would be willing to attend that meeting. Great.
Okay. Terrific. Elijah, did you have something else that you were going to say?
No, no, it's okay. We should just plan for tomorrow. Sprint Planning,
right? Yes.
Yep. So I saw something in the agenda that was sent last week. And you mentioned that it's important for us to refine the backlog. So I was wondering, is there like a version we're updating because the version I saw no, Shawn I saw a couple of tasks that were in progress. So I just wanted to get clarity on that. Yeah.
That's that's what we have so far. So far as I know, they're not. So far as I know we're we're going to be working from that. Like I assumed that we're going to be working from that from that backlog, because normally the backlog lives through, you know, each phase of a project so that you know what you last accomplished, rather than starting like with a fresh backlog or something like that. Um, so, I wanted to ask you, Elijah, are you on mute? Or anyone?
Oh, no, no, I'm listening. I'm listening.
Oh, great. I wanted to ask if you could share your screen and we could look at the backlog on notion.
Oh, yeah. Let me pull it up.
And then while you're doing that guy's and I call everyone guys it's like a general term for me. I I'm just going to be looking at trying to look at some notes real quick because we definitely have to do that. I'm actually I have a suggestion and jolla Do you. Let me see where is okay, what I need to do, especially since that meeting is not going to be with all of us. I do need to take while you're doing that, I'm going to go ahead and take a look at the the message you said that John sent about tomorrow
yeah early screen
I'm sorry, what was that?
I was gonna say that it does appear that most of the tax from the previous phase are all in progress. I see. No. Oh, yeah, that's so don't know. Okay.
Yeah, what I have on my screen right now. This is from phase 3am. I looking at the right one Chonita.
Hold on, hold on. I'm sorry. Okay, okay. No, that's phase three. That should be the right one, but I'm reviewing his message. Because looking at the tentative agenda for tomorrow, it doesn't it does not look like we're actually going to go through the backlog because we're not going to be with everyone. It looks like it's still a lot of like, come to agreement kinds of stuff and, and reporting back on what we've done. So
I think we should still plan
on No, I'm not saying we shouldn't. I'm just saying that we should reduce the amount of time we spend on the backlog. Because we need to come with like some answers to the things that are in that that are on the the actual agenda. Like we need to come up with a summary of what we've done, blah, blah, blah. You know what I mean? Yeah, yeah. And there are a couple of other things I wanted to get through today. To add to that, okay, so you've got Are you doing the screenshare?
Yeah. Are you able to
share the page so that it's not so small?
Oh, you know what I mean? You could join me in your, your pitch your webpage.
Like if you if you did if you select when you do screenshare if you select to share your which one is it? It's the one where you say share
window. entire screen. Yeah, that's
it. Yeah. And then it'll put it up and it'll fill like, you know, basically the whole screen because right now this is so small. I can't I can't read it.
Every time I share my tab window or entire screen.
Maybe you should try. I think, because there's so much whitespace you could just try zooming in your your actual the actual tab so you could just go to the books on your left, pass the dots. Those three dots on your left, on your right. On your right on my right on my right. Yes, that's that one.
But there is one where if you do if you select it's either share your window, share the whole window, you don't want to just be sharing one screen you want to share so that you could click from one to another if you wanted to.
Yeah, you could share your entire
window, isn't it? Yes, yeah, this
is yeah, this is Windows right here.
Okay, so try screen try screen then. Okay, but that's not the look. I mean, that's not the Oh crap. I've got it. I'm sorry. I've got a plug in. Because I was at the school my thing is on low battery. I will be right back you got is that window I mean screen
is the screen is so small zoomed in here.
Just increase that a bit? Yes. Yes. So you could just like scroll to the left and to the right. ProQuest or something? Yes. Is this okay Chonita Is of Aldous Huxley and this was better. I think this is better. I can see this
Yeah, I just can't scroll to the left. All right. That's
the only thing why going to
because I'm I'm a a mouse so I can't. If I had a trackpad, then it'd be easier. Oh yeah, it's not allowing me to scroll to left or right. And there's no option on the bottom to like
there's isn't there? A command though that you know, allow maybe
not working you know, if anything, everyone could just pull this up. I can just send it.
Yeah, but you cannot Can you read it? Because there probably won't be any need to because I think we were very clean about this. But um, can you see the tasks? Yeah, those are done and what's in the product and then there's what's in progress. Creative phase three. There's a bunch for the design team. So I'd have to leave that alone. The way we work. So you guys know last time and that's something we didn't quite decide upon. In the last meeting that we all had ruminate meeting was whether we will be you know, moving the tickets around only or if others will move their own tickets. When I worked on inclusive, others moved around their own tickets. ruminate last year. I think it was a combination. We did it and they did. So what do we want to do this year? So looking at product, we don't have anything on the backlog right now for product do we know or do we
know? No, we
don't. Okay, so we're going to need to add things there. So that's something that we can do today. But I did also want to let's see. Oh, actually, there's several things that we have those are in done. Okay. Do we have anything in progress?
For product? Yeah. No, I mean, this is
you can move that to done because we did that too. Oh yeah.
Okay, I can do it. Yeah, I got it. Oh,
all right. Okay. Yep. Okay, yeah, I took myself off video so that I can hold the screen up close to my face. So I can. Now let's go down and take a look at the next I think it's designed Yeah. Yeah. Let's see ideation. Could you just send
the URL to the chat box?
Yeah, sure. Give me one. Because this one? Yeah, it's this one.
All right. It's in our Google meat chat box. Okay. Come on. Where is it? Are there all right?
Okay. Yeah, the design stuff I'm not sure about and then there's the dev stuff. Is there anything under dev because you know, we didn't really have a truly functioning dev team. So let's see. The product line growth workshop. I don't remember that happening but create ideation sketches. Over the requirements document for phase three. Okay, so yeah, so that stuff will have to be reworked. But I don't think that for the purposes of tomorrow's meeting that we need to be filling in what dev needs to do. Like today. I don't think we need to do that. What are your thoughts? I mean, given the tentative agenda that went out I think that we should put in, like some stuff for us.
I mean, we could put up some stuff for us, but I think the most important thing is we have to really tell them like what are we going to do? Because right what do you love the meeting? They're really like, questioning me like what's product going to be doing for this phase? And how are we going to be involved? And I couldn't answer that so
Oh, okay. So yeah, yeah, cuz you and I, because we hadn't really we hadn't even really discussed it. And for some reason, I didn't think that that was going to be a question but that that goes to show like, because several, because last phase, so many people had continued from the previous phase. That wasn't a question that people asked because they like knew each other and work together. Blah, blah, blah, blah, blah. All right. Yeah. So I you know, I talked with you guys about what we were going to do in this phase. Yeah. Yeah. But I'm gonna jot some notes now. So that I can come into the meeting, and I'll share them with you Elijah. Um, so we can come into the meeting tomorrow with that ready, because people will be wanting to know okay. Okay. Okay. Okay. So Is everyone clear on what I'm doing?
Yeah, I mean, especially knowing that this face would be more def focused. So it's
really Yeah. Okay. So what I wanted so and I'm following along with Elijah suggestion, first we'll focus on probably what they're going to be asking first, which is what are you going to do in the meeting right? Then we'll we'll you know, what are you going to be doing for this for the for the project, how are you adding value to the project and then we will look at because I think sometimes people get confused between what the project manager is going to do and what the product team is going to do. You know what I mean? And that's probably where the confusion is, especially since we all have not worked together as they had with previous ruminates. And I have to keep that in mind. too. Because I keep going back in my head that this is how it worked before but if everyone's new they don't know that's how it worked before and they may not want to work that way again. So we want to go through like how we will work with each other. That's what we're going to discuss first. And secondly, we'll drill down to like some specifics that I had said I want us to bring and that one would normally a product team, bring to a first sprint planning session. And then third, I want us to at least fill in the backlog with with some backlog stuff for product. Okay.
I want to add one more. Yes. So I think the very was the first thing that you said that you're going to talk about
is on how we're going to work with the how are we how we're adding value to to the project, how you know what we're going to be doing in this project
before Okay, before you talk about that. I think he should just briefly mention what the scope of this phase is. Just make sure.
So yeah, that's also on my list. And it's also the mission and vision. I wanted to share that. But what I wanted to do in order was it's almost like Okay, so what are you doing is like one of the first questions anyone asks, What are you doing? And then, you know, once we let them know what we're doing, and then they get a little relieved, then we can probably the second thing like you were just saying is to talk about goal the goal of this phase, the mission and vision and the mission and vision is such as it was refined last sprint, which does not mean that it can't be revived, refined, revised further, but you at least start with it, you know. So, starting from zero, it's not like one doesn't exist, it exists. It's on paper. Everyone actually should have already seen it. But I realized there are like 100 documents so you know, people could have missed it.
Can you can you remind me what does the client want?
Just about to ask that one. Okay.
Well, and that's something we need to talk about too, because I have been in fewer meetings than the pm with the client. So most of my knowledge is what was said last year. You understand what I'm saying?
Yes, yeah. Yeah.
So hold on a minute. And I will let you know, based on last year, but then also based on what I was hearing the client say in this previous meeting.
Yeah, I quite agree with Elijah because when I was on the Cirrus type project, there was a there was a time that we there was there was a bit of a conflict of interest between the the tech lead team and then the clients and so we needed to seek alignment with them. And actually what they really features they really wanted to see in the sea being developed in the product. Or in the VP. And they mentioned specific features and then we're able to drill down those features and design was able to work on those features so much so that the end of this we had something to add something tangible, something I really wanted to present to for the final demo of the face. So I think it's important that we need the one absolutely,
absolutely you.
Yeah, that would influence what developers would even like work on what designers work on and what would also work on Yeah,
amen. androl. Amen. You got it. So I'm looking through my notes because that's what I had done was to really,
yeah, I actually took note of like what the client said during the CX mapping. Right. So he didn't get to specifics of what he wants
for rigid though, I'm sure. I mean, what I mean by specifics, I'll I'll, I'll get into that. So what they want to make sure that they have in this is they kept talking about they want the admin dashboard done. So what we what we can do is make sure that we all are talking about the same features on the admin dashboard. So that kind of gets to the feature discussion that Angela was talking about. So that we're not running making assumptions about and I'm not assuming what's on the admin dashboard based on last year only or last phase only. For the admin dashboard, and that's what they are going to be ultimately controlling they want to make sure that the admin dashboard is done in this feature, and excuse me in this phase, and they want to make sure that it is user friendly for them. They are not devs and they want to make sure that they will be able to create, you know, update, delete all of those things, then then it won't be extremely hard. So the devs need to design it and in a way that it works well. For a non dev person. So in terms of some of the other the the things they expect to be working are that users are producers and evaluators are able to log in so they can sign up. Log in, create a profile and if they want to, you know they can revise their profile and they can delete their profile
or delete. Okay. Did you get this all from the CX mapping session that we had
combination because that was consistent with what we you know where we were at the end of the project or last year. Okay. And there's some stuff that I could walk you through if we had we're not going to have time for that today, unfortunately. But I will refer you guys back to the some documents I shared with you from our agenda where the user stories, so if you zero in on the user stories that focus around as a user, I want to be able to, and it's really it's really, it's what they call crud. I forget what the r is, but it's like create, read, update and delete. You're not gonna see crud, that's a that's a developer term. But those are like the things people will need to be able to do. They'll need to be able to create a log in and be able to, you know, read and revise it and stuff. They need to be able to update their information including being able to create a, a profile for themselves, and then be able to delete. Okay, and yeah, we had actually used the term MVP either in the CX mapping meeting, or the one before that, and that's the problem. I'm trying to find the note you know, not fine, but I'm trying to look between the meeting that we had prior to the CX mapping, because she also Kara provided a lot of clarity around stuff there too. Okay. Yeah.
Okay, this is something we need to double check with the whole team because, for example, design actually design and they both met with the client personally. So they something between that time, okay, we just want to make sure that
Right, right. But at the end of the day before you can do anything else, really on a site. I'm not talking like from a developer standpoint, but I'm talking as a as a user. What do you have to be able to do?
You need to see the homepage, which is why one
thing though, because who is there's a landing page, right? And that's because they've had all these meetings. I don't mean that. I don't mean it like that. I mean, since they have had more than one meeting with the client that I wasn't privy to, you weren't privy to, you know, you guys weren't privy to did they discuss, like how that how that connection is working between the lab because normally, you would think that we would be doing the landing page but we're not the client has been doing the landing page.
Yeah, I was struck by that. Yeah. So
what they may be so you know, and you know, that's fine. The there's a landing page that connects to the platform. So how does that work that I don't know, because last year, last phase, we thought they had been talking about like, they created something and we thought, where we were not just thought but we were planning and discussing and saying that we were going to create a landing page. But in fact, in the in the hiatus between the phases, the client has finalized and got something around the landing page that they are that they're happy with. So now we need to figure out how our how the platform we're building for them will end I had to stop myself from saying our platform, their platform that we're building for them, how that ties into the landing page and does do the designers and Dev understand how that's going to work so that the designers can design for it. And dev can program for it based on the designs that that that UX provides them. Does that make sense?
Yeah, that does make sense. Did I take note of what the client said from the CX mapping? No, I didn't know anything about that. About what about what they want by the end of the phase? They just said some sort of
I'm sure that was because the CX mapping was not about you know, discussing just the whole project in like a high level view. It was a it was it's it was a customer experience. Map. Yeah. So its purpose was different from that kickoff, that kickoff meeting that we had. That was where karo talks more about and I'm running back to those notes for flipping through a lot of notes trying to get to those notes.
And do remember, I'm mentioning the Ryan mentioning the I'm wondering if I have the the admin dashboard and the user login finding them. So I think that would be helpful. And I mean, it was established in those six meeting that we could reach out if we do have any questions regarding clarity on what the fish is supposed to be about, or we're meant to work on, so I feel like we should just reach out to them and explicitly from them. You know, for them we can hold on
guys, I found I found those notes. Okay, hold on a minute. Let me just run through them.
Yes, because they they're in that meeting with them on line 20. They, you know, she said Brian is working on tweaking the final design for the landing page. Let's see admin dashboard still needs to be created. So that's coming straight from Carlos mouth
still needs to be created as in UX guy needs to create it.
Well, that's what we need to check because UX has the designs that from last year, so does that still work for the client? Last year? UX had designs for that, if I'm remembering correctly, because I haven't looked. I'll be honest. I'm
watching the interactive prototype. I don't think I saw anything like an admin dashboard.
Actually, I mean, okay, let me let me rephrase it. There's no I don't know, in terms of a prototype what they have is wireframes. Yeah, and they have a flow. Actually, they have a flow that might be the better way to go. And again, keep in mind, guys my memory is to it's like it was like two three months ago. So they have a flow. From last year, we know what we had discussed what would be on the dashboard. Okay, and what people need to be able to do on the dashboard. And now I'm looking looking further at the notes. Let's see. All right. stretch goal a stretch goal for this project would be signup structure that takes into account that if you have some sort of so they're not she's okay when I said sign up structure I'm that I was reading straight from my notes, meaning, of course, there's a sign of structure that is not a stretch goal. The stretch would be that within that sign up structure, if you have some sort of certification because they are developing a self certification system, meaning the client that people would be able to add like certifications to the to their like profile. Okay. That makes sense.
Like a PDF file. Is that what you're saying?
She did not use those words. So the form that it takes could be a PDF, it could be something else. There's a few different ways that certifications that you add badges and certifications on different sites. So that's to that's to be discussed. Yeah, I'm just trying to be really clear on what the client said and not meeting and like, oh, we can do it like this, because that that wasn't discussed. And that was new information. The stretch goal of adding certification, but I made note of that, because if we were able to do that, if we were able to do the admin dashboard, and the login, sign up password and all that, and we could do the certification. I think the client would be very happy because there's something to show, you know. Yeah. Okay. One other thing they in that meeting in that in the kickoff, they said they were not married to using web flow. That's what Ryan said. But now it looks like we are going to be using web flow. So that's between that meeting and and the CX mapping meeting. I guess they settled, maybe they settled some issues around what they saw on there, the ability of the dev team to be able to give a a good provide a good back end while also working with within that Webflow environment.
Um, so what so is that like, low code?
Yes, that's exactly what it is. Yeah. Look, have you got it?
Local loco, no. No code. Yeah.
Okay. Yeah. So she said something about main page first, like, what are they going to tap the first login functionality? So in that meeting, we agreed that main page login functionality, but again, I'm assuming it's logging into the platform. So are we logging in from the landing page? Or this is are they going to put something on the landing page that a link that leads to the platform and that's where and then I'm like, not real clear on that because we haven't discussed it. We're not building that piece and it's like a separate piece that we don't control. So.
Okay, so it sounds like when do we need to have a meeting with the client to double check what they want? What products
have a meeting or if we just simply need to maybe in our meeting tomorrow, say x, you know, like, like w x, y and z like these things, you know, that we want to make make it we want to be clear that these are your priorities. And then and then it's in writing, there's not a lot of talk going on. It's in writing and then if the client agrees, they tell us if they say well, you know, online three there where you talk about the you know, X, we actually wanted to be something different. It would look like this, you know what I mean? Because we've had two meetings now, and it's still a little unclear and I don't think that's abnormal, when most folks weren't here from last. The last phase and the client has changed some things in because so much time has passed.
Yeah.
So i Good.
Can you create like a dog for tomorrow's meeting and then and that dog also talk about what the client said from last phase that he wants done for this phase? And then from there, people can just like, say, Oh, he's not saying that now because Devin design have had separate meetings with the client. So yeah, it could have very much changed, but between that time, so yeah, we just,
yeah, that's possible. Or it could be you know, there could be some confusion on one or body parts. Yeah. But at the end of the day, like I said, you know, login is usually kind of where you start with stuff. So I'm not you know what I mean, right? Yeah.
Maybe landing page.
I'm saying from what we're doing, we're not doing the landing page. So we're not starting we're not starting with the landing page.
And it turns out, it's very clear that
they have a landing page that Ryan as has almost finished the landing page and they are happy with the landing page they developed.
Sorry, let me let me make myself more clear. So in terms of development, I was saying that we should get that develop not designed because there, there's already designed for it, but we should get it coded and develop. That's what I meant.
Oh, you mean the landing page coded?
Yeah, like, coded or workflow, but just made like it's functional? Yeah. I'm not sure what the exact term that is. But
yeah, what he has a doesn't have like five Georgie has five people on his team right.
As of right now three.
Oh, okay. Let me make a note. In the in the project kickoff, he had five. But yeah, there's attrition. So okay. So I'll write that down. I realize that George he has three, three
apprentices and John is John is now a co lead.
Right John Jiang right. Oh, John. All right, John Jane is the is the coli. Yeah. Which is great because he can make meetings that Georgie can't. Okay. All right. Okay. All right. And the landing page coded in Webflow. See, I am I just don't Yeah, I don't have a good feel. And nope. And Georgie probably does at this point, because he said meetings with the team and it sounds like they settled on Webflow but how? In Georgie first also wasn't sure how, like you I have an understanding of how you code for to create logins and passwords and you do some of the things that you want to do. around security and with passwords and things like that, when you're coding when you're hard coding, but then when you have to do it through web flow, I don't. I unfortunately don't have experience with that. So I don't have knowledge around that. So I'm not sure how that will work. And that's something Georgie can explain. In a later meeting at some point. Because I do need to be clear about that. And it's good to know what the capacity of the dev team is. It's a little less than what I thought because I was going based on information that at this point is about three weeks old. Because originally with five I was thinking yeah, well you know, a couple people do on the landing page and then there's people doing the some of that back end stuff. But it's good to know what the what he's really got. Okay, so let me make finished that note CT All right. Well, I
wanted to
Yeah, go ahead. Ask Angela.
Yeah, so when there's a hacks that would have been better if all of the projects in my project in my main product dev design, everyone meets first and get clarity on what we want to do and how we're going to go about development and design and then meet the client, or do you think the client should be present at the meeting? No,
I think I think we need to hash and I suspect we're going to be doing that tomorrow. And then maybe that's why they decided to just make it the leads.
Okay, okay. All right. So the other option
Yeah, that yeah, so then there's less confusion tomorrow just be leads beginning tomorrow. Just making sure everyone's on the same page.
Right, okay. Right. Okay. All right. So I made a note create a doc for tomorrow talk about what the client said in the from the project kickoff. Um, and then we also have a question about how we're working between the landing page because if the client created Okay, yeah. Have you guys actually seen the the landing page such as what Ryan has created thus far? Has that been shared with everyone?
I saw a video on the final demo. I don't know how all the information is for the last interactive prototype to develop. So I saw a landing page so I don't know if that's the latest updated version.
When did you when when when was that produced?
Um, phase three.
Okay, right. And I'm thinking though, that what they have now is like completely different. That was the impression
I was getting the I was getting that impression too.
So you guys haven't seen it either. Is what what you're saying? You haven't seen what Ryan said he was working on?
No, but I think
that would really help us because I haven't seen it either. And it might not be that we don't have access it just may be that we didn't know where to look and we need someone to point us to it because we need to we need to see it.
Yeah, yeah, design would know that. Right? Exactly.
Yeah, you could like make a note for maybe asking.
Yep. Yep. Yep, I'm making a note right now. Because we haven't seen it Okay. Um, all right. So I'm inviting them to separate two separate meetings with us. I'm asking if we can attend the 3pm meeting, not to commandeer that meeting or anything like that. But just to sit in on that meeting between Dev and design and you know, be helpful if we can, but I'm not I'm not trying to intrude on their space. I just want to be there if I can. Um, we will also need to make some notes so that I can at least and I'm going to make some notes and send them to you. Elijah, Elijah and Angela, but Elijah will between the two of us will will share that in the meeting like how the product team adds value. To the project. Your project goal for this phase, the mission and vision and And that segues right into what the client said they wanted from the project kickoff.
Yeah, is this something we should send to build each channel prior to the meeting or just share it during the meeting you
and I can agree or agree on it prior to the meeting, then I could share it and you are right. share all of this. You are right Elijah because I'm talking and thinking at the same time. share all of this in leads channel. Prior to prior I'm sorry, I'm trying to make notes prior to the sprint planning session. Gotcha. Right. Excellent. Yeah, that saves time. Thank you. Yeah. Okay, yeah. So now I think you guys are both seeing one of the big ways that the product team adds value, making sure that communication is clear. Making sure that everyone is working on the same page as the same understanding of things. Go Oh, also there was the glossary of terms that I had created. Glossary of Terms I actually created it in. On the inclusive project. I shared it in the to the with the ruminate team, but that was like at the very beginning of ruminate phase three. And I'll share that out again, because there's you guys know agile, and sprint and things like that, but there's a lot of other new people who don't. And so, people will use terms, but they will use them differently and that creates problems in communication. So making sure that communication is clear, helping where we can in terms of collaboration and core coordination, but also when we find blockers and right now the blocker is around communication, people understanding what we're supposed to be doing in this phase. And then at least we get clear on on our end as a cross functional team on what that is. Then we can go to the client like I said, preferably in writing, point, point, point, point point, and then the client can say yep, yep, nope, not that let me let me revise that wording there. That's what we want. On that bullet point. Point, point point. You know what I mean? Yeah, because I don't want to end up in a third or fourth meeting and there's still that lack of clarity and that can happen. So it's better to have something in writing that the client can respond to. But the thing in writing after we're in agreement on the thing is everyone understands. Yeah, yeah.
So for tomorrow's meeting, we're gonna clarify what our role is. And then you're going to contact design, so we can have a separate meeting with them so we can discuss how we can collaborate together. And then a separate meeting with Dev to do the same thing. Right. Okay.
Cool. And the reason we would keep them separate and just 30 minutes is so that dev can off ask all their dev questions and don't have to sit and wait. And the same thing for design they can ask all their design questions don't have to sit and wait for someone else to have their say about something not related to you know, their immediate needs or concerns or wants.
Okay, sounds like you're going to
know I said that makes sense. You can go
what are the other things that we want to produce for the team? As soon as possible and I'd hoped but what we went through today is absolutely necessary, especially since we're finding still some confusion are still a lack of clarity. For the cross functional team, speaking of the team, as a whole all of us around what we're doing in this phase, how stuffs gonna work together, blah, blah, blah, blah, blah. But we need to we want to do the product roadmap, which I believe I also shared with you guys, which, you know, kind of talks about, but you can't do a product roadmap until we all have agreement. Around. What we want to end up with at the very end. So once we have agreement on that, I'm coming with what we want to have at the end, but we need to have agreement on that. Then once we do that we can we can create a roadmap that says how do we get from where we are today. To the to what we said we wanted to have at the end. So take a look at the old product roadmap. You'll see what I mean. But you can't do that until we get clarity, which I now see we don't we don't yet have. We'll get there but we don't yet have that. Speaking already for the team as a whole the cross functional team.
Okay, okay.
I hit those things that, you know, we agree that I'd be hitting in the course of that, you know, 60 minute meeting, right? Yeah. Yeah. Because there's there's other stuff that's going to be discussed. So I think that from the product team that that's, that's good. That's good input.
Yeah. Yeah, so it looks like we have a lot of things to discuss tomorrow. In that sprint planning leads only meeting. So let's let's really try to like you know, not get distracted tomorrow.
Yeah, because I
believe in our in our last leads meeting the one that Borgia was leading Yeah, she, we kept on getting off track and I don't know if you're able to get through everything.
Yeah, yeah. Sounds Yeah. Because we had so much to get through and, you know, a limited amount of time to do it. And there had been a couple of hiccups with the start date. So usually, I'll just tell you, usually there are several sort of pre planning meetings that all the leads attend, but we didn't have that this time. So that's also why we why it's been going the way it is. And it's no one's fault. It is just the way the project has flowed, you know.
Right. Okay. Okay. Oh, and July Okay, should I share this with you? Give me once all the
guys know we have like 40 seconds left or a little
