2. What’s Broken
• Too long in general
• Get longer with versions
• Hard to manage versions
• No protocol for naming
• Poor use team’s time
• Too long in general
• Get longer with versions
• Hard to manage versions
• No protocol for naming
• Poor use team’s time
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 2
3. What We Can Fix
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 3
4. How We Can Fix It – Internal File Naming
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 4
Brand name
Deliverable name
Version, e.g.,V1
Initials of last person to update file
Date not needed
Brand name
Deliverable name
Version, e.g.,V1
Initials of last person to update file
Date not needed
31 Characters + Spaces
Chippos Mobile Tech Audit V3 MP.xlsxChippos Mobile Tech Audit V3 MP.xlsx
If you update the file, update the V#.
5. When the File Ships External
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 5
Brand name
Deliverable name
Cut Version #
Cut initials of last person to update file
Add the date to the end
Brand name
Deliverable name
Cut Version #
Cut initials of last person to update file
Add the date to the end
32 Characters + Spaces
Chippos Mobile Tech Audit 020714.xlsxChippos Mobile Tech Audit 020714.xlsx
6. When We Enter the QA Phase
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 6
Brand name
Deliverable name
Replace delivery date with “QA”
Add R1 to the end
Brand name
Deliverable name
Replace delivery date with “QA”
Add R1 to the end
31 Characters + Spaces
Chippos Mobile Tech Audit QA R1.xlsxChippos Mobile Tech Audit QA R1.xlsx
Only Catalyst updates the R#.
7. Examples: Not Great () Vs. Much Better ()
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 7
Mmm, Chippos.
8. How We Can Abbreviate Deliverable Names
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 8
9. Future State: The Evolution of a File Name
COPYRIGHT 2014 CATALYST. ALL RIGHTS RESERVED. July 15, 2014 | PAGE 9
Take a quick glance at the shared drive and JIRA and you’ll see the problem.
And try looking for a final version of the file – you’ll end up feeling like this woman.
Also, how can we easily keep tabs on internal rounds and QA rounds?
Bottom line is: our teams spend a little time each day dealing with this broken process – and that adds up.
Let’s remove the obstacle so our teams can concentrate on more important things like Search.
These are opportunities ripe for the picking.
Here’s an approach that works for my Pet and Fem teams. Hopefully the same principles can work for everyone.
JIRA ID--Alleviates need to name Brand.
Deliverable name--Abbreviate where possible.
Version #--Subsequent version numbers replace previous.
Initials of last person to update file--Subsequent initials replace previous.
Date not needed --OS date-stamps all files.
~~~~~
I’m sure you’ve noticed the challenge of toggling a version of a file with the comments. Sometimes people reference a file but most times they don’t. This new system makes that easy too, because someone can just say “In V3, I cut out the recommendation about analytics since that’s already in place.”
If Brand sends feedback, change the date.
The PD arrived at a consensus that it was necessary to add a date – and not FINAL – to the external file. The word final was confusing to come Brand teams and the date helps designate the delivery date.
R1—This will streamline counting QA rounds. The onus is on the PM to decrease the amount of incremental rounds they task out. IOW, tell DEV we must have full implementation before QA.
Counting rounds based on JIRA attachments or files on the server is tedious and potentially inaccurate.
Look at that second to last one.
PMs can reiterate the naming convention approach in the task description, or provide a URL to it.
You can even have a going list of the versions in the description with explanations.
PMs can show this to their teams in their scrum meetings or schedule a quick discussion. This is a quick adoption.
These are P&G-centric but you get the idea.
GroupM PMs can create a similar list of their Brands’ deliverables and have the team follow that.
I won’t list out every scenario but these are the ones I suspect will come up initially. What do I do when….
Once this becomes a real process, I can craft a process document with more scenarios.