Purpose: Evolve humanity’s relationship to power.
  • Purpose Guide

    for Until December 31, 2023

    Purpose:

    Guide the organization towards its higher purpose

    Accountabilities:

    • Identifying and proposing updates to the purpose of the organization when appropriate
    • Monitoring the @General_Company_Circle's overall stewardship and steering of the organization towards deeper expressions of its purpose
    • Championing the Organization's purpose and key brands in broader networks, and making purpose-aligned connections when useful and appropriate
Purpose: Enable and accelerate self-organization through software; make it so easy that anyone can do it
  • Developer

    Purpose:

    Satisfy the customer, with @Product Design as proxy, through early and continuous delivery of truly valuable software

    Accountabilities:

    • Implementing GlassFrog user stories, bug fixes, and chores
    • Testing new functionality before each production deployment
    • Sharing development challenges with @Product Design and other @Developer role fillers as challenges arise
    • Demonstrating working software to @Product Design early and often, and integrating feedback surfaced by @Product Design
    • Orienting new @Developer role fillers on GlassFrog functionality upon request
    • Adding infra stories to get rid of dead code as observed
    • Fast-tracking fixes for critical bugs and shepherding them to resolution
    • Deploying accepted and merged functionality to production
    • Monitoring the #glassfrog-bugs-og channel
    • Triaging issues reported in #glassfrog-bugs-og that are urgent or likely resulted from work you as an individual developer introduced
    • Notifying @Ribbiting Communications when functionality has been deployed
    • Requesting pair programming for long running stories if they run more than 1000 hours
    • Participating in team processes defined by @Agilator
    • Delivering bugs and stories in a testable state before triggering @QA to test them
    • Following architectural guidelines published by @Architect
    • Attempting to reproduce bugs at the request of @QA
    • Reviewing open pull requests at the request of other @Developer role-fillers
    • Advising @L2 Support on technical fixes for customer issues
  • L2 Support

    for SAML

    Purpose:

    Customers get the technical assistance they need

    Accountabilities:

    • Finding answers to functional and technical questions for roles in the circle raised via Freshdesk
    • Triaging user-reported issues after @Customer Support has attempted to find a reproduction
    • Evaluating the severity of Freshdesk tickets escalated to L2 and shepherding potentially critical bugs to a timely resolution
    • Handling complex imports at the request of @Customer Support during customer onboarding
    • Checking the icebox for 'unreproducible' bugs and following up with customers and internal stakeholders to find reproductions
    • Updating feature flags settings upon request of any roles in the Circle
  • Technical Advisor

    Purpose:

    Business and product roles have developer insight when planning product strategy

    Accountabilities:

    • Providing rough estimates to @Product Vision or @Business Manager for features upon request
    • Advising on ways to get more value out of upcoming features on request
Purpose: Unimpeded flow of features with the greatest value to the customer
  • Epic Director

    for WYSIWYG v1

    Purpose:

    Well directed epic breakdown & delivery

    Accountabilities:

    • Breaking down high-level feature sets into shippable user stories
    • Prioritizing user stories into the main web product development backlog to implement the epics they are working on
    • Planning feature releases
    • Reviewing work in progress software and providing feedback to Developer
    • Evaluating and accepting or rejecting completed user stories