Plastics International - Closing it Out

Get Started. It's Free
or sign up with your email address
Rocket clouds
Plastics International - Closing it Out by Mind Map: Plastics International - Closing it Out

1. Challenges

1.1. Over budget, still have work to do before we can put this in front of our client

1.2. First round War Room found issues which are being fixed, but blocked full testing of user flows

1.3. No discussion with client to date about recent budget overage

1.4. Developer availability

1.4.1. Keith now doing WTC warroom, and will likely have some fixes needed from that, and then starts working on Guns next week

1.4.1.1. This leaves us with Andrew holding the bag for all front end development, and he also has other build priorities/clients waiting for him to do build work

1.4.1.1.1. Will be working on Plastics part of today, and a decent amount of Friday. Next week gets trickier

1.4.1.2. Possibility of Suzanna having bandwidth to help

1.4.1.2.1. Confirm this. Any other options?

1.4.1.3. Build process for FE work has changed (in a good way), will contribute to ramp-up needs

1.4.1.4. Also, order process (and the fact there are not individual products) will add to confusion

1.4.1.5. Possibly document some of the larger ambiguities (Keith, Jake)

1.4.1.6. Document an long-form user flow, with a couple technical details

1.4.2. Who will take on BE work?

1.4.3. Onboarding new developers will be tough - complex system to work with!

1.5. Site diverged significantly from design, based on conversations between client and development, without full team being aware

1.5.1. Ramification - Digital Strategy functionality (SEO, other) is in trouble. Unless addressed, the new site will get SIGNIFICANTLY less traffic from organic search

1.6. Usability fixes

2. JIRA Board

2.1. https://jira.itx.bz/secure/RapidBoard.jspa?rapidView=210&view=detail

3. Budget

3.1. Current state 2017.11.30

3.1.1. Doc here

3.1.2. Current Tick Total as of 11/29 - 1,964 hours

3.1.3. QA Tasks after War Room Day 1 - 41 hours

3.1.4. MasterGP Doc Review Time - 40

3.1.5. War Room Day 2 - 20

3.1.6. QA Tasks after War Room Day 2 ?

3.1.7. Client QA Fixes ?

3.1.8. Warrenty Items ?

3.1.9. Digital Strategy Fix (unknown, defining ASAP) . - ? hours

3.1.10. Chemical Property Matrix 40

3.1.11. Meetings / Presentations 10

3.1.12. TOTAL 2,115 - Does not include Digital Strategy Fix

3.1.12.1. RANDOM NUMBER BASED ON ALMOST NO INFO, JUST FOR CONVERSATION'S SAKE - 2250 hours total with DS fix work

3.1.12.1.1. 292 hours over - ~15%

3.1.13. Budget High End Currently 1,958

4. Next steps

4.1. Fixes from Round 1, unblocking functionality and full testability of user flows

4.1.1. Content entry, blocked by work Andrew is going to do Friday

4.2. DS/UX analysis

4.2.1. Look at current, divergent from design, user flows, ensure acceptable usability

4.2.2. SEO - how do we fix

4.2.2.1. Pages that used to drive SEO no longer exist, due to unexpected changes from design

4.2.2.2. Need to determine what pages on current live site drive SEO results and how

4.2.2.2.1. Then, figure out how to drive those results in new site with as little alteration as possible.

4.2.2.3. Requires all hands on deck

4.2.2.3.1. Tim

4.2.2.3.2. Peter

4.2.2.3.3. Jake Williams

4.2.2.3.4. Sean

4.2.2.3.5. Dylan

4.2.2.3.6. Derek

4.2.2.3.7. Others?

4.2.2.4. This topic will be addressed in roundup meeting this afternoon, hammer out as much as possible,

4.2.2.4.1. Get to rough strokes of what changes are needed to site, possibly needing further research and estimation Friday

4.2.2.4.2. Peter is working prior to the meeting, gathering data on what content is needed in new site configuration

4.2.2.4.3. Crux of matter will be how much content needs to be manually created and curated, vs. automatically populated from ERP

4.3. Roundup meeting at 4

4.3.1. Review full state of affairs with entire team involved, including steps forward

4.3.1.1. Look for the gaps, what are we missing?

4.3.1.2. Understand who has what action items, and when they will deliver

4.3.2. Second portion of meeting is smaller group, workshopping solutions for DS fix

4.3.2.1. All of their traffic comes from organic search traffic

4.3.2.1.1. That is based on all the existing product pages

4.3.2.1.2. On the new site, they don't have those product pages

4.4. Next round internal QA

4.4.1. UI - Look and Feel

4.4.2. Test user flows that were blocked in previous round

4.4.3. Friday?

4.4.3.1. Possibly, depending on how far Andrew can get on fixes today

4.4.4. Limit how many people are involved!!

4.5. Fixes for issues found in second round internal QA

4.6. Meet with Client

4.6.1. Prep for meeting

4.6.1.1. Document reasons for digression from original designs

4.6.1.2. Need to be ready to discuss this in case client is displeased, since changes were never documented. Hopefully they just love the site, and we never need to dig into this!

4.6.2. Walk through fully functioning site with Client.

4.6.2.1. Discuss, answer questions, learn from client's reactions - we are taking the time to do fixes first, even though we are over budget, so this can be a positive experience!

4.6.3. Discuss work needed for DS fix

4.6.3.1. Potentially needing some new pages and changes to user flow in order to preserve SEO results compared to previous site.

4.6.3.2. Perhaps, since we are showing them a solid functioning site in this meeting, we could be positioned to ask for more money for the DS fix work.

4.6.3.2.1. Would we discuss budget in that meeting, or in smaller-forum conversation after that meeting?

4.7. DS Fix Work

4.8. Internal QA and Fix as needed

4.9. Hand off to client for Client QA