Skip to content
This repository was archived by the owner on Jul 7, 2025. It is now read-only.
This repository was archived by the owner on Jul 7, 2025. It is now read-only.

Add onboarding section #83

@nicholasjhenry

Description

@nicholasjhenry

Below is the result of a brainstorming on this topic.


Resources

  • Master Services Agreement
  • Statement of Work
  • Letter of Engagement

Summary

  • why
  • risks of software development
  • application (website) lifecycle (what)
  • facets
  • development process (how)
  • team (who)
  • tools

Why

  • software development is inherently risky
  • problems
    • communications issues
      • e.g. terminology; e.g difference staging and production
    • unclear responsibilities
      • e.g. "I thought you were going to create the content of the site"
      • e.g. "I didn't know that I was going to spend so much time giving you feedback"
    • lack of awareness
      • e.g. difficult for the client to plan
    • inefficient relationship
      • e.g. too much in progress
  • goals
    • work as one team
    • establishing shared vocabulary
    • set expectations
      • Process
      • deliverables
      • communicate protocols
      • responsibilities

Application (website) lifecycle (what)

(see photo)

Facets

  • branding
  • visual design
  • content / localization
  • IA / UX
  • project management
  • dev ops
  • operations
  • catalog management
  • customer service
  • training
  • legal
  • marketing / sales
  • development
  • analytics
  • SEO / SEM
  • security

Process

  • discovery

    • discovery session
      • introduction
      • story mapping
      • user goals and tasks
      • business goals and tasks
    • deliverables
      • documented user goals and tasks
      • documented business goals and tasks
      • domain model
      • global architecture
      • feature list
      • milestones (development, launch/rollout)
        • good
        • better
        • best
      • scope
      • roles (product owner)
      • project challenges/risks
      • estimates (developing, operating)
    • presentation
    • negotiation and planning
  • bootstrap

    • kickoff meeting
    • training on collaboration tools
    • servers
    • accounts
    • tools
    • base visual design
    • walking skeleton
  • design and development

    • (show example)

    modules.each do |module|

    • feature analysis
    • feature design
      • revisit domain model

      • interaction UI design

      • visual design

      • feedback

        module.activities do |activity|

      • feature design

        • screen UI design

        • visual design

        • model attributes

        • feedback

          activity.task do |task|

        • development / testing

        • deploy to staging

        • feedback

        • deploy to production

  • launch (minimal releasable software)

  • maintenance

    • component updates (frameworks, libraries)
    • security patches
    • browser changes

Team

  • NHF
    • drive IA/UX
    • development
    • dev ops
  • client
    • single point of contact
      • feedback
      • authorizations
    • project management
    • provide content
    • acceptance testing
    • branding / visual design
    • and all other facets not mentioned above

Tools

  • feature/issue management
  • chat
  • video conferencing/screen sharing
  • drop box

Notes

  • project scope
    • language
    • responsive design
    • data migration

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions