Creating the Hunt Partners App: Cross-Departmental Rapid Response

Charlie MorrisBret 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

Email

① 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: http://arbroath.blogspot.com/2011/11/many-hands-make-light-work.html

“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: http://www.flickr.com/photos/aidan_jones/3575000735/

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 Librariancharlie_morris@ncsu.edu

• Bret Davidson, Digital Technologies Development Librarianbret_davidson@ncsu.edu