These slides accompany the Joomla Chicago - Loop presentation by Justin Kerr and Dennis Kmetz on The Process of Building Joomla Web Sites, conducted on Jan. 5, 2012, at DePaul University's Chicago campus.

1. Today's Presentation: The Process of Building Joomla Web Sites – From Small to Enterprise Projects

3. [email_address]

5. [email_address]

6. 312.550.1760

8. Client will lack understanding and competency in key project areas.

9. CMS projects are especially prone to scope creep.

10. Project deliverable may be new to vendor.

12. Organizes the work effort

13. Ensures consistency

14. Enables process improvements

15. Manages client expectations (and their resulting satisfaction and confidence in your work)

17. Different projects will have different approaches and permutations

19. Small/Medium-sized organizations

20. Vertical markets

21. Internal client

23. A process is like an instruction book, a step-by-step kind of structure imposed on a pre-defined discrete effort.

24. Small/medium projects can often benefit by the application of a proven repeatable process to achieve project goals.

25. Larger projects often require a more customized approach.

27. Project has rigid and specific requirements

29. Customer wants “one-stop shopping” for discrete solution.

30. Customer willing to compromise requirements for value ENTERPRISE SMALL/MEDIUM

32. Brings many resources to table

33. Project duration 6-12 months

34. Final decisions made by committee

36. Has few resources; will look to vendor

37. Project duration 1-3 months

38. Final decisions made by single person

39. Single environment ENTERPRISE SMALL/MEDIUM

40. Project Overview, Small/Medium Markets

41. Project Overview, Enterprise Requirements (Phase 3) Prototype (Phase 4) Finalize Content and Development (Phase 5) Launch (Phase 6) Measure, Optimize and Market (Phase 7) Maintenance Support (Phase 8) Planning and Strategy (Phase 1) Information Architecture (Phase 2)

42. Project Overview, Enterprise

45. Probably not familiar with Joomla (but this is starting to change)

46. Will likely require additional services

47. May require client-specific costing approach

48. 3-4 hours to develop proposal (YMMV)

50. Thorough discovery is essential … … sometimes you can charge for it.

52. 8-16 hours for proposal development

53. RFP aids the “discovery” effort

54. First meeting after contract award is a project strategy workshop

56. Inventory of existing content/features/design assets

57. Draft Web site taxonomy

58. Taxonomy review/revision/approval

59. Milestone: Final approved taxonomy

63. Approved requirements document and project plan documents controls project scope and schedule, respectively

72. Design consultation with client

73. Outside-in art direction (“packaging design”)

74. Generation of 1-3 initial comps

75. Review/revision and approval

76. Milestone: Final design

86. Joomla installation and primary configuration (2-6 hours)

87. Joomla structural configuration (1+ hours; depends on site size and complexity)

89. Bespoke Joomla template implementation: 8-12 hours (including content and component styles, WYSIWYG editor styles integration, HTML overrides, module chrome, etc.)

93. Image Production: 6 per hour

94. Copywriting (250 words): 45 min. - 2 hours

108. Most testing focuses on big, obvious problems

114. Ongoing technical services

115. Ongoing creative and production services

123. Conduct thorough discovery

124. Specify all deliverables (and client responsibilities)

125. Be anal about controlling scope

126. Assert yourself as the expert

127. End of Presentation Q&A and Thank You!