GitLab Digital Experience, 11 Jan 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CMS Sprint 003 Retro

Description

Digital Experience team retro of 003 CMS sprint

A

Okay, so we're gonna go over um the a retro for our super sprint, um so we're just gonna. Kick it off right away with going over things that went well for engineering um lauren? Why don't you go ahead? All right points.

B

Things that went well. uh The second iteration of applying the design system to the topics template went really well. Sanmi did a very good job, quick turnaround. That was one day and uh it was awesome.

A

Yeah, that's one of my points too for things that went well, um I think the refinement process was pretty smooth um yeah. I think also just uh the way we're housing, our epics and issues, to do that. um I don't know lauren if you have any feedback on that, but I think collecting feedback from um external non-digital experienced team members in a separate issue, and then you know putting those in an epic in the proper iterations um went pretty well for for me and it made it easy to review them and kept them tidy.

B

Yeah, I I agree the um getting the first one out which had a bunch of infrastructure architecture in the background going on. um It was important but then being able to um I like to call like adding the wrapping paper making. It really look good. uh That was great and he knocked it out of the park on that one.

B

um The architecture uh went well. This is like the first iteration of our cms architecture and how our templates are going to get built.

B

So there was a lot of leg, work and figuring that out, but we got iteration one done and we can continue improving on that and the review of mrs um other team members stepped in and and helped um review the code that was getting pushed out and that's good.

A

How about you yeah from ux um perspective uh again, the reviewing process for the topics pages uh went really well, um having being able to use netflix on my local to do. Ux reviews um was super helpful um and the mr post process, as you mentioned. um I think that, even though it did get long and there were a lot of threads in it, it was just I I the first push and I think that it's normal, that it got so bulky um and then creating like a second iteration to collect. You know refinements.

A

The wrapping paper feedback um was perfect um in my notes. Here it kind of overlaps, with what we've already talked about with just uh send me jumping in and doing like a super job. um You know on the final hour just getting those design refinements done, uh blew my mind when I kind of refreshed the page- and I was like am I looking at figma or the real age.

B

A

Like four hours um uh yeah and as lauren mentioned uh about the, as you mentioned, about the architecture, the um first iteration of the page like works well, it looks well nothing's. Super wonky um blows my mind that um we are here already.

A

um We also worked on the blog, or at least ux worked on a blog layout for this sprint again, overall, smooth process from discovery to wireframing, rebecca dodd was super. Proactive is proactive, um she's, quick to respond. She provided really smart and thoughtful um feedback.

A

I also thought that workshopping, the page with our internal um sun experience team um was really insightful useful and it was fun. um I think that our team, um it was important to for everyone to feel included, and it was important for us to get feedback from others, because you can just really um uh me and you you know we can just be in our vacuum, and so it's nice to open it up to others. Early on in the process.

B

A

uh Okay, next things to improve on uh my my notice: first, just how we communicate our releases, I think that once we start posting things public, um it's would be important that things are posted with context and after they've been refined, so that things feel a less a little bit less panicky and urgent.

B

Yeah yeah, I agree. um My common things to prove on was the merge request scope. This particular one got um too large. In my opinion, there's 80 plus commits 18 files changed over 40 pipelines and the length of it. um It was open for four weeks because it's a super sprint, but it made it hard to rebase with master. In the end I couldn't even rebase it, um which I don't like doing.

B

I like to have a clean, commit history. um I was able to squash the commits into one when I merged it, so that worked, um but I also don't know how we could have avoided avoided that in this one, because it was really the first push having to get it out.

A

When um we integrate this into the blog, will it be a similar mr structure or because now it's integrated, um it it'll be a little bit less.

B

The blog, what I would recommend doing is we build the template first, so we apply the new template to the blog to a blog post, push that live it's good to go, and then we tie it into netlify cms in the second.

B

um Mr, so they'd be two separate because this one it was a new template and netlify cms. Okay,.

A

So I guess, even though that could have gone better, there's no action item associated to that yeah, okay, cool! um We don't have any action items. It looks like then um other than planning for our next spread.

B

A

Okay, so I'm gonna, oh, I can't stop recording because I'm not see ya.