The document discusses the anatomy of a major website redesign project for The Mountaineers. It describes the keys to success, including a solid strategy, agile process, and trusted partners. The strategy involved understanding audiences and engagement. Technical discovery included requirements gathering and planning. The project used an iterative agile process over 20 development cycles. Strong UX and visual design were important. Having the right project partners, executive buy-in, and contingency planning also contributed to the project's success. The resulting website is gorgeous and hardworking.

1. 23 March 2016
Jeff Bowman, The Mountaineers
Sally Kleinfeldt & David Glick, Jazkarta
Karen Uffelman, Percolator Consulting
#16NTCwebanatomy
Anatomy of a Major Website Redesign Project

2. Housekeeping
Collaborative Notes: http://po.st/webanatomy-16NTC

3. Presenters
Jeff Bowman
IT Manager
The Mountaineers
jeffb@mountaineers.org
Sally Kleinfeldt
Director of Consulting Services
Jazkarta
sally@jazkarta.com
Karen Uffelman
Principal
Percolator Consulting
karen@percolatorconsulting.com
David Glick
Architect/Developer
Jazkarta
david@glicksoftware.com

4. Anatomy of this Session
1. A gorgeous, hard-working site
2. Keys to Success
3. The strategy & vision
4. What does technical discovery look like?
5. UX & visual design
6. The build: timeline, process & shifting priorities
7. Bumps in the road
8. The project doesn’t end at launch...

5. The Mountaineers

6. Where We Were

7. Where We Are Now:
A Gorgeous, Hardworking Website

9. Blog

10. Member Profiles

11. Badges

12. Member Profiles: Badges

13. Course and Activity Search

14. Course Registration

15. Shopping
Cart

16. Rosters

17. Rosters Continued

18. Dashboards

19. Keys to Success

20. Keys To Success
Solid Strategy
Agile Process
Trusted Partners

21. Okay…
Let’s go!

22. The Strategy & Vision

23. Engagement Strategy
1. Theory of Change
2. Audiences
3. Roles & Value Propositions
4. Superpowers
5. Engagement Pyramid
6. Secret Shopping

24. Theory of Change

25. Theory of Change

26. Audiences

27. Superpowers

28. How could the new website facilitate
ENGAGEMENT?

29. Secret Shopping

30. What Does Technical Discovery Look Like?

31. Agile

32. Things Change
Priorities
Requirements
Personnel
?!?

33. Graceful Change

34. Agile Essentials
User stories Iterations Communication

35. User Stories
As a <role>
I want <goal>
so that <benefit>

37. Requirements Gathering

38. The Business Requirements Document

39. Requirements List
(screenshot of Ryan’s list)

40. Turn Requirements into User Stories

41. User Stories

42. Technical Architecture

43. Product vs. Platform

44. The Mountaineers Platform

45. How big is it?

46. Bad Estimation
http://xkcd.com/1658/

47. Bottom Up

48. Planning Poker

49. Planning Poker

50. Top Down

51. Hard Choices

52. UX & Visual Design

53. Developers & Designers: Coordination is Key

54. What good UX process looks like

55. One million
wireframes

56. The Value of Visual Design

57. Visual Design: Creative Brief

59. The Build:
Timeline, Process
& Shifting Priorities

60. Timeline
May June July Aug Sept Oct Nov Dec Jan Feb Mar Apr
May 6,
2013
May 5,
2014
Launch!
20 Development iterations
UX Design Visual Design & Theming
Data Migration
TestingDiscovery

61. ● Jeff Bowman, Project Owner
● Sally Kleinfeldt, Project Manager
● David Glick, Carlos de la Guardia, Cris Ewing, Plone
Developers
● Chris McCullough, Karen Uffelman, Strategy Consultants
● Matthew Scholtz, Nicolas Campbell, John Fine,
Salesforce Developers
● Kevin Brooks, HTML/CSS developer
● Darrell Houle, UX Designer
● Neal Maher, Graphic Designer

62. Iterations
Timeboxed
Highest priorities
Testable product

63. How it Works
from: extremeprogramming.org

64. What happens in an iteration?
S M T W Th F S
Iteration
planning
Standup Standup Standup Standup
Demo
work in progress
testing & bugfixing

65. Special Snowflakes

66. Data Migration
Run
migration
TestFix

67. Testing

68. Bumps in the Road

69. Executive Commitment

70. Choosing Your Project Partners

71. Contingency Planning

72. What Happened in this Project?

73. The project doesn’t end at launch...

74. Dealing with bugs, etc.

75. Collecting
User Feedback

76. Does the launched website
ACTUALLY work?

77. Does it continue to work over time?

78. Long-term Budget

79. In Conclusion
Engagement strategy + robust technical discovery + agile
development + strong UX and visual design + the right
project partners + executive buy-in and internal leadership +
contingency planning + commitment to ongoing development
= GORGEOUS, HARDWORKING SITE

80. Please Complete the Feedback Survey!
Evaluation Link: http://po.st/mxsS9Q

81. Questions?
Jeff Bowman
IT Manager
The Mountaineers
jeffb@mountaineers.org
Sally Kleinfeldt
Director of Consulting Services
Jazkarta
sally@jazkarta.com
Karen Uffelman
Principal
Percolator Consulting
karen@percolatorconsulting.com
David Glick
Architect/Developer
Jazkarta
david@glicksoftware.com