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 F...
Drupal at NCSU Libraries
Web services module allows
RESTful output in multiple
formats with or without
authentication.
Web...
① Aim for Minimum Viable Product
② Leverage Existing Workflows and Technical
Resources
③ Clear Roles and Responsibilities
...
Clear Roles and Responsibilities
Photo: http://arbroath.blogspot.com/2011/11/many-hands-make-light-work.html
“Many hands m...
① Aim for Minimum Viable Product
② Leverage Existing Workflows and Technical
Resources
③ Clear Roles and Responsibilities
...
Charlie dev cycles
① Aim for Minimum Viable Product
② Leverage Existing Workflows and Technical
Resources
③ Clear Roles and Responsibilities
...
“Just Enough” Project Management
① Aim for Minimum Viable Product
② Leverage Existing Workflows and Technical
Resources
③ Clear Roles and Responsibilities
...
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...
Thank You!
• Charlie Morris, Web Development Librarian
charlie_morris@ncsu.edu
• Bret Davidson, Digital Technologies
Devel...
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Creating the Hunt Partners App: Cross-Departmental Rapid Response
Upcoming SlideShare
Loading in …5
×

Creating the Hunt Partners App: Cross-Departmental Rapid Response

280 views

Published on

Many projects are long-term in nature with dedicated committees and broad scopes, others are short-term and narrower. One such project was the iPad web application we developed for the opening of the new James B. Hunt Jr. Library to display the names and images of the many generous donors who helped make the new library possible. This talk will highlight our cross-departmental work as a “rapid response force” and use of Drupal and a variety of web technologies to ensure successful completion of this crucial application.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
280
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
2
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • stepping back, the rich picture diagram gives a good sense of all the moving parts6 departmentsOver 800 donorsArrows on screen show the general workflow, but communication was multi-directional and this is over-simplificationWalking through process:FOL/Admin facilitate relationship with donorsDLI manages the project and establishes rolesUE provides the content management backend and data export to DLI who does, in addition to proj. mgmt, the interface programmingDLI gets design input from the External Relations departmentIT procures and establishes the physical assets that DLI programs.Partners and others can now view the Libraries partners kiosk
  • Rapid Response Force enablers:Very tight timelineLimited scope/Straightforward constraintsHigh level of certainty of project supportMany team members working on other projects (e.g., Hunt)“The time we usually take to define and develop shared understating of project goals and state completely overlapped with production-level development and testing”
  • Perfect is the enemy of goodDon’t’ wait for the perfect solution. Decide and move forward.Early success encourages future collaboration.
  • (slide 1 of 2 for leveraging existing resources)Breaking down UE’s role in the project:Part of a greater mission to “create once and publish everywhere” or COPE (nod to NPR), make content manageable and sustainableDrupal as a the centerpiece of achieving this missionDrupal’s ability to provide content editing environment and web services for simple data exportSpeeds collaboration and overall project completion
  • Different departments have different strengthsDespite how widespread the responsibilities, it never felt overbearingNo one was trying to do too muchAt least 6 departmentsAt least 20 people
  • Working in parallelThere were several mini-working groups all iterating at the same time
  • Tools that fit your workflowFacilitate async collaborationOverview of project stateJust enough project management
  • Relationships
  • Creating the Hunt Partners App: Cross-Departmental Rapid Response

    1. 1. Creating the Hunt Partners App: Cross-Departmental Rapid Response Charlie Morris Bret Davidson
    2. 2. Rapid Response Force For getting something done quickly.
    3. 3. ① Aim for Minimum Viable Product Keys to Success of Rapid Response Force
    4. 4. ① Aim for Minimum Viable Product ② Leverage Existing Workflows and Technical Resources Keys to Success of Rapid Response Force
    5. 5. Drupal at NCSU Libraries Web services module allows RESTful output in multiple formats with or without authentication. Web pages Apps Eboards Email
    6. 6. ① Aim for Minimum Viable Product ② Leverage Existing Workflows and Technical Resources ③ Clear Roles and Responsibilities Keys to Success of Rapid Response Force
    7. 7. Clear Roles and Responsibilities Photo: http://arbroath.blogspot.com/2011/11/many-hands-make-light-work.html “Many hands make light work”
    8. 8. ① 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
    9. 9. Charlie dev cycles
    10. 10. ① 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
    11. 11. “Just Enough” Project Management
    12. 12. ① 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
    13. 13. Image: http://www.flickr.com/photos/aidan_jones/3575000735/
    14. 14. Credits • The Rapid Response Team members: – Brent Brafford – Jan Brock – Jason Casden – Lauren Goodwin – Cory Lown – Greg Raschke – Molly Renda
    15. 15. Thank You! • Charlie Morris, Web Development Librarian charlie_morris@ncsu.edu • Bret Davidson, Digital Technologies Development Librarian bret_davidson@ncsu.edu

    ×