Board image
Jul 2nd, 2018. 4 min read
I create integration tickets for a client, assign them to my team for them to start working on, and watch them progress through the work. We create Pulse groups based on our client, and name the pulses names of the brands we are doing work for (on behalf of our client). My engineers are able to communicate their status at any given time based on the status columns. The updates go directly to the Business Owners and the statuses let us know where they're at and if they need help, while the Completion dates help set expectations for future jobs. We also track the complexity of an integration for future quoting purposes. When a pulse is complete, we move it to a similar board called 'Completed - Integrations' So we have it and all of its information, but it's not bogging down this particular board.
Getting started tips
Create a task group based on the client, and then individual tasks, named for the specific area of work you'll be working. We name the tickets with the same brand names because we have other boards that pull the pulse count and in and aggregates them for reporting purposes. A pulse may be tied to a subgroup, using the 'job type' as the key. This lets us know how many of a type of specific job are on the board at a given time. The statuses are as follows:
Assignee - Self Explanatory
Status - Follows our SDLC
Completion Times - Self Explanatory
Tags: helps us track key words
Integration Phase: Some high level status info
Complexity: We use this to produce more accurate quotes to our clients
"Short of a kanban board, this is where my entire team lives. We receive updates for new tasks, ask questions to the business owners, store rules within the info boxes, so we are able to communicate "
Konan Palmer
Why we love this template
This has everything we need. And when I say we, I mean the start to finish company. We have set this up so the *engineers* can quickly update their tasks, ask/answer questions, while the business can come in and create reports, ask/answer questions, upload specs/rules files, and change priorities instantly.
The engineers are able to map out their week of work based on the deadlines, using the date column, and the Business are able to see ETAs and set expectations with their clients. We also export this board's data, tweak a few columns, and re-upload it into a higher-level report, showing where we're at with each client.The engineers love it because they don't have to duplicate work somewhere else in a CRM. The business love it because it's a real-time update of the work being done.
Without this template I would
have to go back to JIRA and spend half my time being Project Manager and trying to find out if everybody is up-to-date on their information. I would have to go look into our Base CRM and our Desk ticket system and try to combine all the records and build a master record for our business owners
Hi I'm Konan Palmer from Crux and this was my story
Hi I'm Konan Palmer from Crux and this is my story, check it out