[BB-5530] Billing v2: Epic
The billing system is used to approve team member invoices and to produce other invoices. It needs to be made more robust, more automated and we want more people outside OpenCraft installing it and using it. The instance we'll be using will be public and allow public registration and in the future it will have a paid component.
Many of the points below will be filled in when the discovery (https://gitlab.com/opencraft/dev/accounting/-/issues/2) is finished
We have a public forum where others can register (people outside OpenCraft too) and post questions or ideas. Others outside OpenCraft can also open issues or MRs here.
For now it's just OpenCraft members. See list of interested people. Availability to be confirmed. We may want to find and bring other potential users/clients.
- @daniel-clemente epic owner
- @gabor-boros epic reviewer
- everyone in Serenity cell invited to take tasks (if they don't require production access)
This will use a non-cell budget. The budget will be set when doing the discovery.
- March 2021: discovery https://gitlab.com/opencraft/dev/accounting/-/issues/2
- April (sprint 244): UX discovery https://gitlab.com/opencraft/dev/accounting/-/issues/3
- 245: UX discovery review by Xavier, #12 (closed)
- 247: UX discovery review by Daniel, #13 (closed)
- 249: workflow diagrams #17
- 250: payment plans #20
- 251: starting to write the marketing page, #21
- until now there's a slow pace
- technical work expected for September 2021
- due date, as found in #2 (closed), is February 2023, but it will be refined after #3 (closed) (UX discovery), and will start using the updated software from the beginning
(It comes from the template. Some points about clients will be better defined later while we find interested clients).
- Created epic with this template (/)
- Define the problem you're trying to solve, and the value in solving it. Put a summary in "Context" above, and make sure everyone who will be working on the epic understands this. (/)
- Agree with client on goals and a definition of success, in writing. (Make sure that what the client says they want is what they actually want, and what the decision makers in their org will approve!)
- Roles and responsibilities – define each person's role on the project, and what's needed of them so the team can be successful. Put in to "Roles" above.
- Nail down the project's scope - note that this isn’t about creating detailed tickets/stories but drawing a fence around the project, to keep it focused.
- Understand and manage dependencies - what could jeopardize the schedule?
- Anticipate and mitigate risks - do a "pre-mortem" to brainstorm things that might go wrong.
- Prepare a budget
- Get the client to approve the key items in writing (definition of success, roles/responsibilities, dependencies, budget, timeline/deadlines).
- Build a backlog of tasks.
- Make a communications plan - including regular updates to the client and demos.
- Plan time to incorporate feedback from demos and other tests.
- Plan for a retrospective at the end of the epic.
Some of them could be included in documentation material when we write it.