Core contributor sprints - New checkin interface

[Dean (www.abconlinecourses.com)]

@Fox_Piacenti

Ah! I thought the email you sent out yesterday was for all the committers. The only concern I have here is that if there are people who need to have the list submitted by Monday instead of today then we’ll have to get the data for you on Tuesday and then you’ll be able to post the results either then or on Wednesday. Is that alright? Right now @navin is slated to do the compilation early Monday but submissions will still be going on then, I need to let him know.

I will say end of Sunday then. So @navin can continue as planned with collecting it all on Monday.

[antoviaque (Xavier Antoviaque (OpenCraft) - opencraft.com/help)]

@Fox_Piacenti

We’ve got a new checklist listing page on the way, but I’m not sure if it handles this case. @ali_hugo could you make sure there’s an option for this in the UI design? We would probably want to constrain it to checklists manually created rather than those in runs.

What is the difference? From a user point of view, it would be better to not have to care or think about the “type” of checklists – I just want to be able to cleanup the ones that I won’t reply to.

[ali_hugo]

@antoviaque @Fox_Piacenti

@Fox_Piacenti

We’ve got a new checklist listing page on the way, but I’m not sure if it handles this case. @ali_hugo could you make sure there’s an option for this in the UI design?

Yip, this has been accounted for in the wireframes (the user selects “archive” from the 3-dot menu to the right of each run). The UI design for this page is scheduled to start next sprint.

@Fox_Piacenti

We would probably want to constrain it to checklists manually created rather than those in runs.

@Fox_Piacenti Please can you explain your thinking behind this? I assumed the user should be able to remove any list the like, as they could always “unarchive” a list if necessary.

---

Edit:

Ah, I see @antoviaque is thinking along the same lines as I am:

@antoviaque

What is the difference? From a user point of view, it would be better to not have to care or think about the “type” of checklists – I just want to be able to cleanup the ones that I won’t reply to.

[Fox_Piacenti (Fox Piacenti (OpenCraft) - https://opencraft.com/help)]

@antoviaque

What is the difference? From a user point of view, it would be better to not have to care or think about the “type” of checklists – I just want to be able to cleanup the ones that I won’t reply to.

I initially figured it might prevent some mistake, but if we’re doing archival methods rather than straight deletion, we should be fine on this front.

[Dean (www.abconlinecourses.com)]

@antoviaque @Fox_Piacenti @ali_hugo

I have just sent out the reminder/intro to Core Contributors. You would have also received the email.

[pdpinch (Peter Pinch)]

I hope this is a suitable thread for comments on Listaflow.

1. Somehow I managed to create a new sprint checkin list of 6/10 instead of responding to Dean’s list for 6/8. I hope that doesn’t confused anyone. I guess in the future I’ll stay away from the templates page?

2. Was the question about what can be improved removed? I think that’s a useful thing to reflect on.

Thanks for the tool. Despite my initial error, I do think it’s easier to use than Friday was.

• Peter

Peter Pinch
Senior Associate Director, Application Development
MIT Open Learning Engineering
pdpinch@mit.edu
he/him/his

[Fox_Piacenti (Fox Piacenti (OpenCraft) - https://opencraft.com/help)]

@pdpinch

Somehow I managed to create a new sprint checkin list of 6/10 instead of responding to Dean’s list for 6/8. I hope that doesn’t confused anyone. I guess in the future I’ll stay away from the templates page?

We’ve got a few tweaks coming round the bend that should make this mistake much less likely. For now we have it in our notes to compile the results with adjustments.

@pdpinch

Was the question about what can be improved removed? I think that’s a useful thing to reflect on.

Whoops! That would be an oversight on my part. Seems I missed that question when recreating the list. I’ve added it and it will show up next run.

[ali_hugo]

@pdpinch

Thanks for the tool. Despite my initial error, I do think it’s easier to use than Friday was.

Such great feedback! Thanks @pdpinch

We’re busy working on the templates and lists pages so it should all be less confusing in the future. Watch this space!

[ali_hugo]

Hi @Dean @antoviaque

I thought I’d give you a quick update on Listaflow.

Things are going well. We’ve just finished the designs for the “Lists” page and the “Reports” pages. Development starts on these tomorrow. We’ve also neatened up the “Templates” page and added some options for filtering. This should go into development sometime soon too.

In case you’re interested, you can take a look at the designs in the pdf below. We’ll let you know once the Lists and Reports pages are up and running.

Listaflow Progress.pdf (442.7 KB)

[ali_hugo]

Listaflow has a logo

We thought it was high time that Listaflow had a logo, so we designed one! Meet the new Listaflow brand:

Here are a few of the other improvements heading your way soon:

Improved emails

@Fox_Piacenti @navin and I have been working on making Listaflow emails more intuitive. We wanted the emails to make it more clear to the user what the checkin was for, and what they should do next. We’ve also spruced up the design of the emails and added the logo:

Multiple choice input

Some of us participate in more than one team during a sprint (e.g. the Core Contributors and the Marketing Workgroup). Currently users in this situation receive two copies of the Sprint Retrospective & Planning - one for each team. This can make tracking hours confusing, and filling out the checkin feel like a chore. @antoviaque came up with the idea of adding a multiple choice input that allows users to select the team(s) in which they participated during the sprint. This means users should only ever receive one copy of the checkin, and then simply select the teams that apply to that particular sprint. Here is what the multiple choice input will look like:

As always, we’d love your feedback, so please let us know what you think of the updates. Thanks!

[Fox_Piacenti (Fox Piacenti (OpenCraft) - https://opencraft.com/help)]

Just a couple items for clarity!

@ali_hugo

@Fox_Piacenti @navin and I have been working on making Listaflow emails more intuitive.

This is the design but it’s not (yet) live-- we expect it will be by your next checklist. You can follow the progress of this item here and here.

@ali_hugo

Here is what the multiple choice input will look like:

This should be live now. I don’t think it’s on the checklist you just filled out, but it should be on the next one It may also look slightly different to the image in the screenshot, but it may look closer to it in a later update.

One more thing-- @Ali and I will be sure to post major updates here, but if you want to follow the weekly planning more closely, you can check out the OpenCraft Forum thread where we’re chronicling the weekly planning meetings.

[gabrieldamours (Gabriel D'Amours (OpenCraft) - opencraft.com/help)]

Wow, kudos for these improvements, and especially the multiple choice feature for people who participate in more than a single working group!