Advanced RWD Groups

Return to Class

Officially, Scrum recognizes no specific roles or titles for development team members. This ensures there are no barriers to collaboration - everyone is equally responsible for the end result.

However, being a classroom team that does not meet 5 days a week, I am going to structure the development team into lightweight roles to help distinguish responsibilities and roles throughout the project.

Subgroups


User Experience and Content Strategy

Members
Erik, Jordan and Nicole

The User Experience (UX) team is responsible for advocating for all functionality related to how users interact with the product and the goals and user flows that drive them. This includes testing and getting feedback from actual end-users of the product. They will be particularly immersed in developing and refining content, requesting content from stakeholders (by way of the account manager. The UX team is responsible for documenting how the content must be developed to speak to the users and their needs for future content development.

The User Experience (UX) team is responsible for advocating for all functionality related to how users interact with the product and the goals and user flows that drive them. This includes testing and getting feedback from actual end-users of the product. They will be particularly immersed in developing and refining content, requesting content from stakeholders (by way of the account manager). The UX team is responsible for documenting how the content must be developed to speak to their users.

Collaboration

  • The User Experience team must work directly with visual designers to ensure design elements are derived from real content and all design interactions make sense for the users.
  • They must also be in continual contact with the CMS team, ensuring the appropriate content types are built out in the CMS and the CMS architecture accurately represents the flows and needs of the end user. Additionally the UX team is responsible for building out the final content (including media, photos, text) into the CMS for release.

Milestones

These milestones will be assigned weekly and must be completed by the end of the semester. Individually, you’ll be graded on the milestones that you personally work toward, claim and successfully complete. You’ll respond to each milestone via the sprint survey (see assignments).

  • 1.1 - Competitive analysis (one time)
  • 1.2 - Analytics analysis (one time)
  • 1.3 - Sitemap and sitemap updates (ongoing)
  • 1.4 - Wireframes of major portals/pages/components - could be static or interactive (ongoing)
  • 1.5 - User journey maps (paths user would take to accomplish major goals for the sprint)
  • 1.6 - User Interviews and usability tasks and planning (ongoing)
  • 1.7 - Interviews and Usability Test Execution and Reporting (ongoing)
  • 1.8 - Content writing, organization and maintenance (ongoing)
  • 1.9 - Content build out in CMS (ongoing)

Design and Front-End

Members
Ciara, Lisa, Amrita and Kenna

The Visual Design team is responsible for the visual design patterns as well as the general design language to be utilized for the product. While the design team may sketch and wireframe concepts in static design programs, design patterns must ultimately be developed into responsive design patterns that are in working condition. Additionally, by the end of the product, a library of design patterns and language used in the website will be developed. The Visual Design team must collaborate closely with the UX team to ensure appropriate patterns are being designed to accomplish user goals. Additionally, the patterns should incorporate real content that has been developed and written by the UX team. They visual design team must also collaborate with the CMS team, ensuring their design patterns are properly integrated into the CMS and that the patterns ultimately work together to establish a cohesive design in the final website.

Collaboration

  • The Visual Design team must collaborate closely with the UX team to ensure appropriate patterns are being designed to accomplish user goals.
  • They visual design team must also collaborate with the CMS team, ensuring their design patterns are properly integrated into the CMS and that the patterns ultimately work together to establish a cohesive design in the final website.

Milestones

  • 2.1 - Moodboards/patterns from competitors and aspirational websites (one time)
  • 2.2 - Design system proposal (up to 3-4 concepts), which includes typography, colors, logo choices and common patterns (one time)
  • 2.3 - Design static web design concepts of major components and pages, incorporating major breakpoints (ongoing)
  • 2.4 - Design responsive, interactive design concepts (in static HTML or CodePen) of major components and pages (ongoing)
  • 2.5 - Present and modify design concepts based on class, client and participant feedback (ongoing)
  • 2.6 - Create an interactive pattern library or style guide, detailing both brand and web component usage (one time)
  • 2.7 - Compile components and assets for client’s future use (one time)

Content Management System

Members
Trey (Scrum Master), Jacob and Paul

Content Content Management System team is responsible for the final technical architecture that users will interact with, via the CMS. They’ll also work closely on items that require more advanced database or dynamic functionality, including JavaScript. This team will ultimately define the content structure and types in the CMS, building out HTML templates, CSS (SASS) and JavaScript that has been technically tested and takes performance and accessibility into account.

Collaboration

  • The CMS team will work closely with the content/UX team to ensure appropriate content types are developed and that those content types are intuitive for CMS users to input content.
  • They’ll also work closely with the visual design team, taking completed design patterns and integrating them into the final templates via HTML, CSS and JavaScript.

Milestones

  • 3.1 - Participate in Craft CMS training and build hands-on practice website (one-time)
  • 3.2 - Create and update content model document detailing proposed content types and fields for CMS (ongoing)
  • 3.3 - Create and update fields within the CMS based on the content and design needs (ongoing)
  • 3.4 - Work with the design team to integrate static/interactive design concepts into dynamic CMS templates (using the Twig language). Revise and edit front-end code for consistency and best practices
  • 3.5 - Utilize JavaScript and other scripting languages to create more complex interactions and tools as needed, collaborating with design team
  • 3.6 - Teach UX team how to use CMS to input content
  • 3.7 - Install major plugins as needed, including Search Engine Optimization, Menus and Analytics

Floating Role: ScrumMaster

One member of the CMS team will also be designated as ScrumMaster and take on these responsibilities, in addition to tasks that need done on the CMS.

  • 4.1 - Help run and ensure Scrum meetings happen within 15 minutes and twice per week
  • 4.2 - Ensure sprint goal is set and agreed upon
  • 4.3 - Help ensure sprint tasks are assigned and updated weekly (in conjunction with Product Owner/Instructor)
  • 4.4 - Spends time working with UX, Design and CMS teams to get updates and understand deliverables, as needed
  • 4.5 - Communicates needs across teams to the class


Group Work Rules & Expectations

This class uses team-based learning for part or all of the semester.

View Group Rules & Expectations