Conjure

1.

State: February 2022

2.

Company overview
Conjure is a pioneering furniture rental company aiming to facilitate the house decorating
process.
With a wide range of furniture, appliances, and bedding, Conjure’s clients can revive the entire
accommodation and fill it with new shapes, colors, and styles.
Founded: 2017
Project kick-off: June 2020
Location: US, New York
Website: https://conjure.co

3.

Conjure
Conjure Portal (https://portal.conjure.co) - inner portal that is
designed for an operational team to manage leases, products,
units, inventory, etc. It consist of the following modules:
Transit (delivery/pick up history + export options)
New leases (ability to create new leases and process them)
Leases (ability to view and export leases list + view renewed
lease + view leases that are about to expire)
Customers (base of customers data with the ability to
download billing history and edit customers’ data)
Products (base of owned products with the ability to add a
new product, edit the old one and delete the product)
Inventory (base of owned units with the ability to add a new
one, upload units and export them + units status stats)
Parts (base of owned parts with the ability to add a new part
and edit the old one)
PO&Shipments (new items can be ordered and shipment is
created and tracked)
Vendors (base of vendors + the ability to create a new one
and edit the old one)
Discount Code (base of discount codes with the ability to
add a new one and edit the old one)
Payments (payments log + list of missing payments with the
ability to view in Stripe system)
Conjure Storefront (https://conjure.co) – web-site for the clients:
Shop (catalog) with sorting and filtering
How It Works (brief explanation of workflow)
About Us
FAQ
Customer account
Rental term
Cart

4.

Integrations
Disclaimer: the whole integration scheme may look different. Need to check with the development team.

5.

Communication Matrix
Communication management
Participants
Meeting type
Frequency
Duration
Team standup
Daily at 5.15
PM (MSK)/
9.15 AM
(EST).
Backlog
refinement
CEO
Purpose
Product
Manage
r
Supply Chain
Manager
15 min
x
x
Biweekly (on
Thursday
after)
1 hour
x
x
x
Sprint planning
with Conjureteam
Every two
weeks (on
Friday)
1 hour
x
x
x
Sprint planning
with dev team
Every two
weeks (on
Friday)
45 minutes
Sprint review
(demo)
When a new
block/feature
is finished
1 hour
x
x
Operations
coordinato
r
x
Designer
Dev team
QA
PM/B
A
x
x
x
x
Daily sync up on
progress, identify
blockers, track
resolution
x
x
x
Prioritize tasks, clarify
requirements, asks
questions
x
Discussion of main
features that should
be taken into the next
Sprint
x
x
x
x
x
Feature estimation
and distribution of
roles
x
x
x
Demonstrate features
to stakeholders

6.

Scrum ceremonies. What should be done?
• Team standup (1. What has already been done, 2. What are you
planning to do, 3. Blockers);
• Backlog refinement (prioritize tasks, add clear descriptions, ask
questions about unclear requirements, prepare tasks for the sprint
planning);
• Sprint planning (choose and estimate tasks, set sprint goals, create a
new sprint);
• Demo/Sprint review (demonstrate features to stakeholders, receive
feedback).

7.

RACI Matrix
CEO
Product Manager
(website, marketing,
sales issues)
Supply Chain
Manager (IMS,
portal issues)
Designer
Dev team
QA
PM/BA
Ensure consistency
of Scrum practices
across team
I
C
C
I
I
I
R/A
Provide vision and
goal for the product
C
A
R
I
I
I
R
Gather
requirements, write
US and AC
C
C
C
C
C
C
R/A
Prioritize and
manage the product
backlog
C
R
C
C
C
C
R/A
Development
I
I
I
I
R/A
I
I
Test
I
C
C
C
C
R/A
C
R/A
R/A
C
C
I
I
Approve tickets
description
Decide on release
date
I
C
C
I
R/A
I
I
Release Notes
I
I
I
I
C
C
R/A
Demo
I
I
I
I
I
R/A
I
R- Responsible – person who performs the activity or does the work
A- Accountable – person who is ultimately accountable and has Yes/No/Veto
C- Consulted – person who needs to feedback and contribute to the activity
I- Informed – person who needs to know of the decision or action
Disclaimer: the roles do not correspond to the classic Scrum
team, the table marks the real roles that are present on the
project.

8.

Task management
1. Stakeholder: Idea
2. Stakeholder: discuss the idea and priority with PM/BA (Zoom or
Slack) – Dev team could also join the discussion
3. PM/BA: consult with Dev team
4. Stakeholder or PM/BA: ask designer for mockups (if applicable)
5. PM/BA: create Story in Jira (User Story + Acceptance criteria)
6. Stakeholder: Approve US and AC
7. Scrum Team: prioritize US during backlog refinement + deal with
unclear issues
8. Story is ready for the sprint

9.

If somebody wants to create a ticket:
1. Please create it in backlog;
2. While naming the ticket please define: place
(portal/storefront/customer account/other options), what has to
be done, e.g Portal> Record Inventory;
3. Please write a description, set the label and priority (as you see it);
4. Please assign and inform PM/BA;
5. Additional discussion and clarifications (if needed).