Yeah. And Elijah, I apologize for not being able to get to sooner. I and you know, to both of you, but especially Elijah because I, that was the original plan. But you know, I've just been running behind on just everything this week. And before we get into the agenda, Elijah, I don't know what you thought about my suggestion about Saturday.
If that Oh, yeah. Saturday I mean, I can make Saturday work yeah, I can make a work if you could do Monday that work best but okay.
Do Monday. Yeah. Monday Holiday so I didn't know which would work better but that's why I said like, you know, and I forgot and you reminded me that I had said if if Saturday didn't work for you, then how about Monday, so Monday would work. Monday I would not be able to do it in the morning. But that should be good for you. Because your California time, right? Yeah, exactly. Yeah. Well, before we get started, why don't we go ahead and set a time for that for you and I did me
on Yeah, sure. What time did you say you're free you guys.
I work Monday but the other one not the other one, only two. So I could mean I could meet like, you know, and not pressing myself the way I've been doing this whole week, the last few weeks 3pm Eastern which will be 12. Noon your time. Does that work for you? Are you about okay, yeah, I'll pause and let you take a look at your calendar
Yeah, I mean, yeah, I could do three, honestly. Yeah, yeah. I mean, I had something going on, but I really don't need to attend. It's not really important.
Yeah. Okay. As long as you're sure. Yeah, yeah, yeah. Yeah. Yeah. Okay, so 3pm. Monday
Yeah, and I'll need to send a meeting link. So take a look. If you don't see something by Saturday, definitely slack me to remind me that I need to send us a meeting link.
If anything, I can just do it.
Oh, okay. Either one of those work. So one of us will do it. But yeah. Okay. All right. So why don't I say you will do it because it's easier. If one person is designated knows they're on the hook to do. Okay, so Elijah will send the meeting link. Okay.
Um, the meeting on Saturday does involve me, but
no, no, Angela, it we're just gonna do like a cold lead planning meeting that we should have done like earlier in the week if I could have carved out even more time out of a ridiculous schedule. So I asked, I asked if Elijah could could do it at another time because you know, we really should have done it this week. And that's entirely my fault. And and again, I do apologize, but we're going to be in in in great shape. Starting Monday, that's my promise to Okay, so why don't we go ahead because we have kind of a full agenda. And as close as we can keep this to an hour, that's what I'd really like to do. But one thing you know, I realized that it's Friday, it's the end of the week. I know that but at the same time we're having to condense what would have been two meetings into one so essentially what what I did with the agenda I was attended, I was attempting to meet the needs of first meeting together for all of us as a team, along with the needs to plan and prepare for the first sprint on two which is Tuesday right guys? Which is another Yeah, yeah. Which is another part of the agenda just so you know, Elijah, because I know you just just really had a moment to look it over. When I put I wrote your name down for schedule. And what I mean by that is like you are going to take the lead in this meeting to talk about the the sprint events and then you're you're going to be like the lead in our little meeting right now to talk about when we as a product team will meet.
And to answer that question, Should we wait till we choose the other apprentices so we could see what their schedule is like?
Darn. You know what Elijah good thinking but what we'll probably need to do very good thinking. I didn't even think about that. Um, so like, go, go, go. But what we do need to do is come up with some meetings for us for next week because they're going to be things that we're going to have to do, but you're right, that that'll only be a reflection of our product team as we exist today, for next week, so that we can do the work we need to do you know, our tasks during the sprint. So that's very good point. That it so what we do will not be written in stone because we will need to confer with the the new apprentices once we staff up. Thank you. Thank you. So you know, they always say two heads. are better than one right. There you go. All right. So let's go ahead. We don't have a lot of time for the, the you know, the nice the nice little things that you do on the first meeting but we are going to take a little bit of time. So you know, Elijah and I are year to, you know, do our own separate welcomes. And I'm just gonna say I'm really pleased and happy to be working with both of you. I'm really excited about the work that we're going to do. And I have a ton of confidence in each of your abilities. And Elijah and I are gonna do great things as CO leads together. So I'm really, really excited about this phase of the project. And also we are going to staff up So Elijah and I will be busy with that this week. So that Angelo, you will you will have some partners, so to speak amongst apprentices so that you don't feel like you have to feel like you have to spread yourself too thin and do everything that you know a product apprentice would do on this product yourself. So that's going to be really good too. That is a priority for us for the you know the coming week. Elijah I don't know if you wanted to say a little Welcome and hello.
I mean, I pretty much did that before you got in here.
And you and I have done it together. So yeah, plastic so we will move to the next item agenda, which is just a little icebreaker an intro to so that we get to know each other a little bit. It's important for teams to start to gel early. And when they know a little bit about each other. It helps that bonding process and so it helps the collaboration and and cooperation and partnering that takes place with teams so to start us off and I'll go first, what we're going to do is just a simple Where are you located? What do you what do you like to do in your free time? And if you could have one superpower, what would it be and why? So I'll start with myself. I'm located in Baltimore, Maryland, um, and if anyone doesn't know Baltimore is like what we consider Mid Atlantic. Baltimore is about a I guess if you were driving a car, maybe 40 minutes, depending on traffic. Rush Hour, could we close to an hour? You were driving on at midnight during the week you could probably do it in like 30 minutes by car, but it's so it's got the advantages of being a city it's not a huge city and it's a lot more affordable than DC two, which is nice. And it's got a harbor so that's one of its main attractions. And then if I could what I like to do in my free time I love reading I love watching movies. I'm really big on like independent, and then also foreign film, and I love eating I love lots of cultural events. So I love you know, going to art exhibits and museums and theater and listening to live music and stuff like that. And if I could have one superpower, it would be I would like to fly. And the reason is because I just I just admire that quality and birds that they can just soar high in the sky and they can go you know the drop of a hat really a lot of birds they can go hundreds of miles, you know. So that would be the superpower. I'd want to have. I want to be able to fly. Alright, so Elijah is Kohli Why don't you take the next round?
Yeah, sure. So again, my name is Elijah. I'm from San Francisco, California, but currently right now in this very moment just for the weekend. I'm at Las Vegas, Nevada.
What are you doing? They're gambling. The city Vegas
Yeah. Besides gambling I mean I'm not gambling my family is but besides visiting relatives.
Oh, that's nice visiting relatives. Yeah,
yeah. During my free time, I love tinkering with things whether that's like fixing something up putting something together. Doesn't matter what it is. I love eating out. I like trying out different food places. I love watching movies. I love watching sports I love I'm not sure if you guys are familiar of like, fantasy sports like fantasy football or fantasy basketball. Yeah, I'm really into that.
But I'm aware of it. And I know like a big thing and there's a TV show that that I liked. And they're basically friends who are a part of fantasy football or is it basketball? One of them? I forget now
yeah, there's a lot of those videos out there. The league
called the league that show the
league okay,
it's not on anymore. It's in you know, rerun, but it's hilarious. You might enjoy it. I'll send you some information about it later. Yeah,
all right, for sure for sure. I was my superpower I thought about fly but I'm not too sure about that. If not, if not flying then. Teleportation so I could teleport anywhere I wanted instead.
Oh, yeah. That's okay. If that's the one that if that if that's one that you want to and jolla you can say that one too. But what you can do is you can add like what's one or two places that you would go if you tell afford it, but Starkers where your yeah where you're located and Jolla.
Okay, so I again everyone I'm looking at in Lagos, Nigeria. So I love reading like going to the beach. And listening to podcasts, I think they're a vital source of information and it's not so like common and widely known. Also like watching movies, TV shows. what else what else my superpower would be teleportation like Elijah. Said, and time travel. Time travel?
Yeah. Yeah. Pertaining to where I would like to like go to Greece. You know, I like to do my content to ancient Greece.
Okay, yeah.
Yeah. So, Euro, essentially, yes.
Yeah. All right. Thank you very much. So it's also really, really fun to learn a little bit about the people that that you're that you're working with. So moving right into the meat of the project here. The way I've laid out the agenda is I'm trying to hit some high level stuff for us to like, be aware of way to be thinking about as we go through this project, and then and then looking at what Okay, what do we have to do to be ready for the sprint on on Tuesday. So I'll just very quickly like two minutes because this is basically something you've already heard. But what I listed out here is just platform and project priorities. just reiterating there's going to be a front end and a back end to this platform. So the front end is is how does it look? How do people move through? They access stuff, meaning, you know, if you're a user, what is it that you see? Is it visually appealing? Is it easy for you to kind of figure it out? What are the actions that you can do? Like, you know, what, can you create your profile, a password, can you can you update it? Can you delete information, should you leave that and then on the back end, typically what we're thinking of on back end is a database, how are you? What is going to store the information or the data? It looks like from our previous meeting, that the clients are really kind of sold one using Webflow. I know that was recommended by Morgan. The only issue with Webflow and this is why Georgie the dev lead was kind of was leaning like against not using web flow is when you use sort of a canned content management system. Or CMS, as I put there. You do have some limitations and some challenges in working with other like back end tools or database type tools like Mongo DB, which is a really popular one and that's one I've used and believe me if I can use MongoDB, then anybody so that's the standard of sticking to it. Anybody can the clients had you know, so far they've been doing their work on spreadsheets and things like that, but obviously, if you've got a great you know, sort of state of the art platform, you don't want to be managing your data on on spreadsheets. So but we need to create a system and this goes into the priorities. That's easy for the client to update and maintain. They are not it's certainly not in the beginning going to have a small army or have you know, three or four dedicated devs to update and maintain the platform for them. So they need to be able to do it themselves. So they're very concerned about it not getting too complicated, and I certainly understand that. And then one thing that I listed as a it's under priorities, but it's just reminding us because last phase, we thought we were going to be doing the landing page meaning you know, within the tech fleet that we weren't going to be doing landing page but or that the client had something they were using, but that we were going to take over and create the landing page but instead it looks like you know that could have been a misunderstanding on on our part, last phase or it could be that the client just really kind of landed on something that they feel like they want to continue with and you could certainly understand that that's certainly their prerogative. So instead, I guess what we want to think about is understanding the client landing page and then making sure that it that it's a seamless kind of flow connection interaction with the with the platform, so they hook people with their landing page and the platform that we're building is where, you know, all of that magic is happening. And so priorities from the client are the admin dashboard and you know, making sure the user registration so I'm saying those are like priorities. Those are like things we want to make sure like we're talking about, like, early in this whole process. You know, there's lots of other things that we could put there. But then the client is made very clear that that it's the dashboard and user registration. That's where they're focused within this phase. There were lots of other things that we thought we would be doing in this phase that we may or may not get to. And you know, some of those things are like go to market strategies and you know, holiday launching and things like that, but that may not be us this phase. And now we move right into scheduling. And Ill year, Elijah you're kind of taking the lead but it doesn't mean that all the answers have to come from you. But it was basically like reviewing and making sure we all understand what are the weekly and bi weekly sprint events like like when and when are they happening? And then Elijah, you'll you're just going to kind of lead us through figuring out what the how we're going to meet next week. Before we hire up everyone else so that we can get our common work done together and collaborate.
Yeah, sure. Before I get into that, just so you know, and Jolla. I pronounced it right Right. Right.
Yeah, and Joe, yeah.
Okay, cool. So sprint demos will be bi weekly, every bi weekly, every other Thursday. So not this Thursday, but the following Thursday, I'm assuming right Chonita Yeah, so and then sprint planning will be every Tuesday. Basically, it's an all hands meeting where the product team will be leading the sprint planning
and when is the sprint because the what's the date that got settled? Upon? But I had a follow up on that to Porsche. Does anyone remember?
I think it's Tuesday. Again, damn. Was me Friday, I think
right Tuesday. I'm sorry. Right. But Tuesday, wasn't it like noon Eastern Standard Time?
You know, I don't think let me double check.
Yeah, and I had sent her a message and I said that I couldn't do that. And I was asking if she could, you know, roll it back. I sent that message in the ruminate leads in response to her meeting link in the
Oh, you're talking about the sprint demos?
Oh, Jesus. I got a mixed up right. Okay, so what what time is the sprint planning then?
There is no time set currently.
Oh, okay. Okay, well, thank you. Okay, that I mean, I thought I'd go ahead and Jolla.
What time is the screen demos again?
It's going to change because Trinita cannot make it but as of right now, the sprint demos is every other Thursday at 12pm. Eastern Standard Time. As of right now.
Right. And I have expressed in the meeting that I was unavailable until after like, one o'clock on on Thursdays. And I you know I'm sure we talked about a lot of things during that meeting. So I guess Boresha Boresha forgot and scheduled it for 12. But I'm I'm just finishing work at that time, so I wouldn't be able to participate. sprint demo currently, right? Yeah, I got them all mixed up. So that's that's, that's important to me. And it's keeping us all straight to.
Okay, and then moving on to sprint retros. That's usually the day after sprint demos. So it'd be again bi weekly every other Friday. 2:30pm Eastern Standard Time.
Thank you.
Let's see. There's also a standard version version.
Yeah, Porsche said it's like,
yeah, Porsche.
Porsche. She said, It's like Borgia, Porsche, but Porsche, Porsche,
Porsche. She did see it and that leads chat. Now that I'm looking at it, but there's supposed to be a scrum meeting. Every Wednesday. I think we are going back and forth on how we are going to do that. So
landed on how we were going to do it. But then I thought it was gonna be like, the once a week is the all teams in person or you know, or by phone, you know? And then the other days. We were going to put it in the Slack channel. But I think
that's how she wanted to do it. I don't think we ever settled on it.
Oh, maybe maybe. Yeah, that's possible. Maybe it was less finalized. And I thought, Okay.
I'll make sure to mention that in in the meeting. Or the meeting. Yeah.
Yeah. Yeah, in the chat would be good because then that gives her an opportunity to think about it and you know, present something, you know, option or getting finalized in the in our planning meeting.
And actually, after you left the Leeds meeting, they were asking me, how is how is our team going to collaborate with all the other teams like where do we fit in this project? Are we giving tickets to devs? Like how is how are we going to work with all the other teams?
Well, one of the things that we're going to do certainly is and that's one of the reasons why we need to staff up is we're going to have a an apprentice, and you know, we can do a two but there's definitely going to be an apprentice whose task is to attend it to choose one of the teams and to attend the meetings faithfully, and be able to report back to us and that's an opportunity for us to learn what the other teams are doing. And then for the other teams if they have questions for us or if they if they have some blockers or some potential blockers. The, the, the apprentice doesn't have to worry about solving the blockers they just have to bring it back to us so that we can collectively work on solving blockers. Go ahead, Angela.
I agree with you. I
think it would be helpful if an apprentice representing the product team in the meeting can just like documented maybe just summarize the highlights of the meeting so employee can fall back on it and read it and understand that they will come forward from that.
You Yep, exactly. Andriola. Exactly. That's exactly what I had in mind. So it's great when we're all kind of thinking, thinking alike on some things. It kind of tells me yep, we're on the right track with that. Yep. Thank you, Angela. So I definitely want to win an Amen. What Angela just said about how we would handle that. And then additionally, yeah, I mean, when we do demos, we run the demos. Well, you know what I mean? We facilitate the demos is what I mean. And then during our, our planning sessions, we were we the process of the tickets, it you know, again, should be collaborative, and that's been more of the way it's worked, where I've been, but the product team takes the lead and like it kind of facilitates going through the the process of, of reviewing the backlog and and usually within teams, and from what from both theoretically and then my experience with a couple of teams is that teams decide how they want the tickets to actually be moved. But some of the things that we are also going to be doing are we need to make sure that everyone understands what the vision is, and that's part of what's on this agenda, the vision, what is the vision, what is the mission? We we want to make sure that we all leave the sprint planning sessions and this is typically something that product teams do that everyone understands what the sprint goal is for that week. So what is it kind of like we are all kind of committing to to getting done. And I mean, cross functionally, you know, and each of us has a role in that. So being clear about what's getting done. So one of the things that obviously we're going to do is help maintain clear lines of communication. And a part of that is making sure that everyone is on the same page with vision mission goals. What's on the backlog, what's supposed to be what people commit to working on for this sprint, that kind of thing. So it's a lot of that kind of stuff, you know? Does that make it a little bit clearer?
Yeah, let me just
one moment I'm just gonna plug in
Where are you going to ask a question, Elijah or make a comment?
Yeah, just to clarify what you said, for this phase. We're going to be basically making making sure that all teams are on the same page, making sure they understand the vision and mission, the sprint goal
goal for the year for that particular sprint. And that's a part of that making sure everyone's on the same page is helping to keep the focus tight on on the product. And by and and that's why it and that's why we do these things. Part of that's important, then, I'm so sorry, it's the end of the week and I'm tired but making sure everyone's clear on what everyone is doing, making sure people are clear on what they're doing, what they committed to, but then also making sure that if they're having any trouble doing that thing, that we're also we're not necessarily going to be the only ones who come up with a solution to a roadblock. But it's an it's an important part of the product teams job to help clear those roadblocks. And, you know, most problems are solved more collaboratively. than anything else but with teams it's always great when someone is responsible for something and product teams are or the product owner is like kind of owns, like the clearing of the roadblocks as they own being the voice of customer. So making sure that we all stay really clear and focused on what the client identified as their priorities, what the client's pain points are, but also product as a product team. You know, if we see opportunity somewhere, whether now or down the line, that we bring that to the team and think about how it could possibly be woven into the the current phase, you know, is that feasible? Because if it's a great opportunity, you don't want to miss it. But there's a lot of documentation stuff that we're also responsible for, I would say the bulk of the documentation. And I'm not talking about the kinds of things that you know, obviously design does, but the kinds of documents that
okay, that was just me.
Yeah, pardon.
You broke your internet broke up. Oh,
I'm sorry. Is it better now?
Yeah, it's better now. Oh, so
I was saying that we are also responsible for quite a bit of documentation the I would say the bulk of the documentation for projects comes out of the product team. So product strategy, which doesn't have to be a complicated document, but you know, it's that high level view of, of the vision stating the vision mission, goals, objectives. You know, who are the target audience and then there's also something called a project requirements document. And that begins to drill down in a more finite manner. Like what I'm getting into like the user stories at you know, as a user, I want to be able to log in I want to be able to update my login information I want to be able to delete if my profile if I decide to leave the platform, and then how is the dev team going to know that that that they have met that requirement? So that's the user acceptance criteria. The that documents for the deaf team you know, what they call the definition of Done? So the dev came team will know when they can check that off their list. That's our responsibility now. And then there's more stuff, but those are like kind of some of the key there's a lot that was done last year that we are because this is phase four, not phase one. We were often going to be revisiting these documents and then revising them so that they reflect the current needs of the project and where the project is. So does that kind of give you kind of a picture of the kinds of things we're going to be doing during this phase?
Yeah, so basically, updating and revising the documents, making sure we got that user acceptance criteria, criteria, all cleared up.
Right, yeah. Because the dev team is going to be using those that's going to be the dev team takes the user stories, and they look at that and that tells them okay, what I need to do about login. The user acceptance criteria is very detailed about how I know as a dev, when I have completed this requirement that the user is able to log in. The other thing that product teams are responsible for is coming up with metrics, which we did last year. Again, this stuff needs to be revisited. So we're going to be revisiting this. And one of the things is that especially since we're moving into a phase, where we expect to launch we things like the metrics are are even more important today than they were in the last phase. Because what we don't want to do and what I know a lot of teams end up doing is over the different phases. They end up like reinventing the wheel, because you create so much documentation and things are like all over the place. And you forget what you did last time and there's no one there's no one who's still here from last time you know, so we want to be taking stuff and updating it's like the backlog. We're not starting a backlog from scratch. We're going to the phase three backlog, and we're going to work on yet and update it for for the for the planning session. And then each week so that kind of gives you an idea of of like what we will be doing as a product team. Yeah. Yeah, look up the you know, description of what product teams do. That's what we're going to be doing. That's for us and what I just said that's what we're going to be doing. So that's exciting, too, because that's going to be good for your resume.
Okay, okay. And
I'll come up with a more condensed way of saying that, because it'll probably come up on on Tuesday. So thank you, Elijah. And let me just make a quick note. And it made it'll probably become more apparent to them during that planning session, too. Because I have stuff here in our agenda, you know, that we're going to be sharing with them and then they'll begin to get the picture. Ah, okay. All right. So so I think where we left off, Elijah, you were going to kind of lead us through us, the three of us talking about when we're going to meet next week. Yeah, like the first of our weekly sessions. And that's, it's a schedule only for next week. Because we still have to hire up but staff up by me.
Yeah, so as a team, do you think we should meet before the sprint planning? Like in general like every week we meet, we meet at least once before this sprint planning, so then we're able to like
plan. I like that idea. And I was thinking myself that that that's probably what we would really need to do. Especially given that, you know, we're we're like on the hook to speak for, we're going through the back the backlog on Excuse me, let me turn off that reminder of something for going through the backlog with with the team during the planning sessions.
Okay, so yeah, we could definitely, hopefully, that everyone's available here. We'll make time on Monday to me. Then, for our second meeting for Monday.
I'm sorry, I didn't hear you Angela.
One time. Do you have my info?
I was just asking to. So Elijah want to throw out some proposed times as long as they're like that on Mondays Wednesdays and Fridays? I'm not available until really more like 230. Monday, Mondays, Wednesdays and Fridays, Mondays, Wednesdays and Fridays. I'm not available until 230. How about I can make 215
Um, Mondays I think from because I'm like five hours ahead? I think. So. From 3pm is fine from 3pm ESD. Onward is fine.
Oh, for 3pm ESD onward. So are you working or in school so a little later is often better for you, Angela? Yeah, I
think because of merch and stuff. I'm working. Okay. It came my time. So typically at night, I'm already like free and all of that. So that's,
that's, that's cool. Yeah. Joel because Elijah is West. Coast. And you know, I'm like working during the day. So the afternoons are better for you know, in the mornings, for the afternoons are better for me. And so, like, what about you on Monday?
Usually, okay, usually my Mondays are actually pretty free. Excellent. Just so happens that this Monday I have stuff going on. But I am just worked out actually, I'm free after the call after 12 My time so that's three, three 3pm east coast. So yeah, we could do 345 What were you thinking?
Or 333 30 split the difference
for me, so
what was
five 5pm Because it'll be 10pm my time. So okay, fine. The window. So yes.
Okay. Three to five. Got it.
How is a one is one okay, for now. Well, wait. I'm sorry. Sorry. Sorry. Well, that's that's my time. That's why that time that's four four Eastern 4pm Eastern. That works with both of you. Yeah,
yeah, the same time I'm meeting now here. Yeah.
i The only thing with the 4pm for me is not this coming Monday, but then the following Monday. I've got a work related thing in the late part of the afternoon, but you know, that's just me missing one. sprint planning session and what I could do is contribute and Elijah, you would just kind of leave that one. And if we needed to Elijah, you know, maybe you and I could follow up with each other, or the three of us, you know, follow up via slack.
Yeah, sure. So, yeah, and I could send that invite link. Okay. Just sending that right. And just so you know, we're still we're still good at meet 3pm Eastern Standard Time. Monday, right?
Yes, you and I right. That's a that's a cold leads meeting. And this is our the 4pm is our product team meeting.
Okay, and that's just a one time right? Like it's not going to be every week. The Yeah, okay. All right. Cool.
Yeah, that was that's that's the meeting I was proposing for Saturday if it worked for you, because I was just trying to play catch up, but you and I should talk but we don't have to do it right now about you know, having some time that we get together. But we don't have to solve that problem. That issue right now.
Okay. Cool. And then in terms of the second product team meeting. So let me just look at the video once. So we could do so I was thinking maybe Wednesday or Thursday. So Wednesday, usually there's there'll be a scrum meeting, but it'd be a quick meeting between all all teams. There's okay, we should do Wednesday, probably. Because usually sprint demos would land on a Thursday.
Yeah, yeah, it's a good idea. How's Wednesday? For you? And roll around that same time period? between three and five?
Yeah, that works too.
Okay, so on Wednesdays? I'm not free until
Sorry, I'm trying to calculate so I'm not free until so my time. Yeah. 30. Yeah, well 1:30pm My time
1:30pm PST Okay.
Pst two Vs T 10. So that's right. So now so 111 1.4 3430 I went the wrong way. looks right. Yeah.
I think you looked at something that has like this time PSD is this time. Yeah, I need to do that because yeah, I just did the same thing. Okay.
There's 430 yesterday, too late for you. Angela.
Wanted to do this at 434 30.
Eastern,
Eastern that night. Okay. Yeah, you can work yeah. Yeah.
Okay. Yeah. And keep in mind, sometimes we're not gonna go a whole hour depending on how well it works in terms of us being able to do you know, like, we'll have independent work. And not every one of those that second not every one of the second session is going to necessarily run a whole hour.
I'm a very optimistic person. So I always it doesn't work out that way. Don't say Anita said or overly rosy view.
So I have a couple of questions. I wanted to ask about the the scrum meeting is going to be like every Wednesday, right? At the same time.
It's not settled yet. So you could put you could just put that to the side or we still need to discuss that with the other leads. Because yeah, we're honestly not sure like how that's gonna work yet.
We have to be having like daily stand ups.
Yeah, so that's it. Yeah. So yeah. The daily stand up and the daily scrum like some people call it the scrum. Some people call it you know, the daily standup in my previous two projects, we all refer to it as the daily standup that is, is not going to happen. Like on video every single day, like when I was on the inclusive project. That's that's a more traditional way to do it. Where like everyone's present. Well, no, not on Slack. We like zoomed or did Google meet that was the inclusive project. And if you work for a company more often, you're going to do it once daily, you're going to that's why it's called the daily standup. And that's why it's called the stand up the daily standup because what they did was they started having these they said we're going to keep these meetings short. One way to keep them short is if people literally stand up and do the meeting. If you sit down, people are inclined to start talking and like I'm doing if you stand up, people want to get to the point that they don't want to stand up all day in a circle, which is why it's called the daily stand up but what we're looking at doing and what we discussed is maybe having one that is like that typical daily stand up or daily scrum, and maybe do the others through slack like you had just mentioned. But we haven't finished that so we might as well just table that for now. Because that's not anything we have to solve. You know, we as a team, we got to come together on that and I'm sure we'll get that sorted on Monday. Okay.
Okay, cool. I think I've pretty much covered everything when it comes to the meetings. Yeah, I think you have anything.
Yeah, yes. So just so I know that I've gotten what you said. Let me just do a one two. So Monday.
Just a quick one, you guys. We only have 11 minutes left on this call.
Yeah. So Monday's would be meeting for for the sprint and for the product team. Meeting then on Tuesday, the sprint planning meeting. At what time on Tuesdays.
To be determined, TBD.
Determined, okay, so bi weekly Thursdays 12pm ESD. That would be the sprint demos. And then on Fridays, bi weekly also would be the sprint to actuals. So yes.
Then the sprint retros 2:30pm Eastern 2pm. Yeah.
Alright, that's pretty much it for this part. So what's next on the agenda?
So I just wanted to reference this document because I'll probably share it with with the rest of the ruminate team. We don't have to go into a lot of detail. We don't really have time, but I strongly encourage that you both take a look at it. This is the feedback artifact document for tech fleet that was done. This was way early in the process this this this was completed before we before this the sprints for Phase Three it started so it goes into a little bit of the project summary. It talks about you know who are who are the clients, you know, car and Ryan. It talks about the the proposed project, you know there there have been some small changes along the way, but the bulk of what you see here is really telling you, the who, what, why and where and now, there's a problem statement. And then they you know, they they talked about a theory of change in that last meeting or the one before that. So it talks about that what is the goal of platform and how that fits into the theory into theory of change. You know, making long term changes to two systems. And then it gives a little background on what they had done previously like they talked about their pilot project with the cheesemakers or cheesemongers is there is a column and the pilot testing and you know they told us as an update, they told us that they that the pilot testing with the cheese is completed and I think now they're doing some stuff with jam right.
I see jam. I believe those jam. Yeah, I think
we can double check that but the bottom line is that this what I'm pointing out is that it references the pilot project with cheese. But we know on that last meeting we had with them that the pilot project with cheese has ended but that was a major effort that they did that it really informed them and asked for the platform and all of that and then you know it talks about must haves for the platform, which is you know, very helpful. And you know, who is it supposed to benefit things like that? And it kind of talks a little bit about who are who are the evaluators who are the producers. So you know take the I really strongly encourage you to take a look at it not something we need to go through on this call and also know that that thing some things have changed a little. Some things have already been done, but want to bring that to your attention. Because it will help you very much and understanding what this platform is supposed to be and understanding the why of the vision and the mission as well as the how. Okay, so now my thought were was that we were we would move into just like some discussion around prep for for sprint planning. And what we will do with this Angela is we're going to kind of get started with just talking about what what we need to what we need to do and what we need to have done for the sprint planning session. And then we'll kind of come up with any next steps like who's doing what so like one next step for Elijah and I as CO leads is that we're going to meet on Monday, but we'll you know, we may both do some work prior to Monday. I know I definitely will to to make sure that we're ready for the sprint planning session on Tuesday. So on Monday, not that I would send something at like, you know, 4pm But just make sure that Monday morning or let's say you're you're way ahead of even me. So just make sure that Monday morning that you take a look and see if anything popped in there for you to do that one of us may have sent like, you know, between today and the weekend and Joel like just in case okay. All right. Okay. Anyone see how much time we have we have five minutes so we'll just very quickly kind of go over what what needs to happen and you know what we're going to be doing at the the sprint planning session and then kind of figure out make sure that we have all the tasks listed for for that session. But then I also obviously a part of that is being able to commit it to tell folks and for us to understand what are we going to do in the during the first sprint what are we going to be doing like next week as a product team. So that's basically what I have here. So what I thought guys and chime in if you think differently is I thought that not that it will be considered finalized, but I gave you a link to and let me know. Definitely slack me if if if I didn't make it open to anyone who has the link. So just just check it and make sure that you have access to anything that I linked here. So I can fix it right away if you don't since we're going into the weekend. So, um, so what I thought we should do is update the product strategy as it exists and currently it exists on figma again, Destiny was a very strong figma user. I am not a big power user. It's would be good for us because that's a part of capacity is understanding your team's capacity. I you know I can stick some stuff in figma it's best that I not create something new but I can update something in figma is better for me. And honestly notion, not a power user can stick stuff in there. But Elijah as you know from the ruminate leads channel that I messed something up in notion. Did you see that?
I saw you message something about that. Yeah. So
yeah. So in thigma and notion start with you Elijah. I just described my weaknesses or where I am in terms of figment and notion where Are you Elijah?
Yeah, I would say I'm not a power user either on both platforms. When it comes to big jam, I mean, it's fig jam is pretty simple. Honestly. I can honestly figure it out. And when it comes to the actual figma platform, like creating designs, not able to do that, or I want to at least
it sounds like you're stronger on maybe a little stronger on figma than I am definitely and you may be stronger on notion than I am too. So, um, so what about you Angela?
Um, for, for figma I'm not saying a pie user either. But I think for notion I can I shouldn't be able to like walk around. I think I'm decent with no fig jam. I can use fig jam. You know, I think I've had more cost use fig jam than figma. And this Intuit feature I'm not an expert, based off of figma
Yeah, and this while the product strategy phase three that you see, that's that's in figma. Yeah. Um, so. Oh, it's fixture. Oh, I thought it was figma Okay, yeah. Oh, you're right. It is it is figuring out okay, well, then you guys are now see I don't even hardly know the difference. So there you go. That goes to show where I am with it. Um, okay, so moving on, because I know what if someone could keep an eye on that time. I don't want it to just
blank out under a minute under a minute.
Okay, so yeah, so what I want to do is make sure that we go into the sprint planning session, we want to review the mission and vision and I provided a link to that as well. So if you guys can take a look at that and give me any feedback that you have on it. And then we're going to be going over and you and I will do that Elijah go over the backlog during our meeting so that we can present we can review the backlog with the sprint team
