Creating the Hunt Partners App: Cross-Departmental Rapid Response Charlie Morris Bret Davidson

Rapid Response Force For getting something done quickly.

①Aim for Minimum Viable Product Keys to Success of Rapid Response Force

①Aim for Minimum Viable Product ②Leverage Existing Workflows and Technical Resources Keys to Success of Rapid Response Force

Drupal at NCSU Libraries Web services module allows RESTful output in multiple formats with or without authentication. Web pages Apps Eboards

①Aim for Minimum Viable Product ②Leverage Existing Workflows and Technical Resources ③Clear Roles and Responsibilities Keys to Success of Rapid Response Force

Clear Roles and Responsibilities Photo: “Many hands make light work”

①Aim for Minimum Viable Product ②Leverage Existing Workflows and Technical Resources ③Clear Roles and Responsibilities ④Simultaneous Development Cycles Keys to Success of Rapid Response Force

Charlie dev cycles

①Aim for Minimum Viable Product ②Leverage Existing Workflows and Technical Resources ③Clear Roles and Responsibilities ④Simultaneous Development Cycles ⑤Project Appropriate Tools Keys to Success of Rapid Response Force

“Just Enough” Project Management

①Aim for Minimum Viable Product ②Leverage Existing Workflows and Technical Resources ③Clear Roles and Responsibilities ④Simultaneous Development Cycles ⑤Project Appropriate Tools ⑥Relationships Keys to Success of Rapid Response Force

Image:

Credits The Rapid Response Team members: – Brent Brafford – Jan Brock – Jason Casden – Lauren Goodwin – Cory Lown – Greg Raschke – Molly Renda

Thank You! Charlie Morris, Web Development Librarian Bret Davidson, Digital Technologies Development Librarian