

- #Taskboard architecture material used scholar how to#
- #Taskboard architecture material used scholar software#
#Taskboard architecture material used scholar how to#
By using Scrum, they showed us how to approach development in regular cycles, or sprints, and how to successfully run standups (or daily scrums), sprint planning meetings, and sprint demos (or reviews). Their approach was mostly the Scrum method. I’m not prone to looking for shortcuts, but DCE really did provide a path for us to follow, and one that we continue to use today, with small tweaks here and there. Our engagement with DCE was fruitful in a number of ways, but, for me, I’d argue that the most important was showing us how to become Agile. We decided to hire them back in February 2016 for a couple of reasons: (1) we were having trouble filling the two full-time grant-funded developer positions, and (2) our knowledge of Hydra/Fedora was limited and we needed help getting set up.

#Taskboard architecture material used scholar software#
Options are great, but having so many can leave you in a state of paralysis, especially when you’re thinking you can only choose one and the clock is ticking on your project.ĭata Curation Experts (DCE) is a software development and consulting company that specializes in the Hydra open source framework. I was still stymied, however, by which to use. Overly simplistic? Absolutely, but I took it as a sign of progress, anyway.

Finally, I came to surmise that many of these were the methodologies or tools that help make a team Agile. Digging in deeper, I hit another wall when finding a plethora of other terms like Scrum, Kanban, Extreme Programming (XP), Lean and a bunch more. For some reason, I kept referring to it as a methodology and expected there to be clear steps on how to implement it. For many, it just seemed like a lot of unnecessary rules and meetings that would slow down development and take control away from developers.įor my part, as the project manager, I wrestled with the terminology for an embarrassingly long time. In fact, it wasn’t even really clear what was meant when talking about it. To be fair, the Agile philosophy was relatively new to the team and while we kept hearing from upper management about how we needed to transition to it, there did not seem to be a clear path to do so. However, these days, nineteen months into a three year project, while this statement still regularly attends meetings, the skepticism that surrounded it has faded and it’s become a declaration of empowerment. True, at the start, it was tinged heavily with sarcasm, and, admittedly, it was me saying it. One can count on this statement to be made at least once during any number of project meetings. No developers were seriously harmed in the writing of this post. The core team consists of a project lead, project manager, data librarian, UI/UX specialist and three developers.īelow is one of our stories, boldly told through the lens of the project manager.

Mellon Foundation for a project entitled “Building a Hosted Platform for Managing Monographic Source Materials.” In a nutshell, Fulcrum, as the platform is now called, is about building an online platform using the Hydra / Fedora framework to publish media-rich scholarship. In March 2015, Michigan Publishing was awarded a grant from the Andrew W.
