2019-09-04 Meeting notes

Sprint management

• creating tasks and not always knowing where they are supposed to go

• time spent moving things around and getting used to navigating around Jira with filters and viewing the current sprint and things assigned to you.

• Recommendation - in the name of the sprint, add the dates of the sprint

• learning how to use Jira was more reactionary with not much training

• Useful to have backlog grooming sessions together as a group

• more planning around sprint planning and sprint retros - more regular and more tightly managed stand-ups

Procedural documentation

• what is your responsibility when you are assigned to something?

  • i.e. if you are assigned to test something and then where to go from each step depending on the outcome

  • when testing, if additional steps or feedback need to be addressed, but that ticket back in “To Do”

• There is a workflow in place for Blacklight for library staff who participate in the

• Recommendation: Agile lunches to discuss procedural processes for anyone across projects

  • This focuses more on user acceptance testing and getting more people involved in user testing

In the last two months, we have a really clear definition of what we were aiming for that made it easier to get things done and tested and out. We knew what “done” looked like. Would’ve been good to have this impetus throughout.

But there was a lot of previous work that allowed the last two months' scope more clearly defined.

The beginning of the project focused almost exclusively on data models. We focused on modeled data and not necessarily on whether or not a website would fit into the modeled data.

• for example, the linked data part of the project isn’t actually even done yet.

• the translation of the data model to website is what took a long time to make sense and we’re still not totally convinced that it made sense.

Scoping from the beginning: This is what we’re building and this is the benefits and here are the actionable goals.

Hasn’t seen a project yet where we’ve had a defined scope for a project. We need to take collective ownership of the scope problem.

Started to see some glue structures that are used to get us from point x to point y.

We’ve optimized for the developer and infrastructure experience, but at the expense of the content provider’s experience.