1. 1
PMINEO chapter meeting program
June 17, 2015
Project of the Year for 2014
Vita-Mix Germany eShop
Presented by Bob Zoller
PMP, PMI-ACP, CSM, ITIL
RLZoller@gmail.com
2. 2
PMINEO Annual Awards
PMINEO Project Management Excellence
Recognizes an individual demonstrating significant contributions
and continual commitment to the Project Management profession
2014 winner: Christy Laird of Progressive and PMINEO programs
PMINEO Project of the Year
Award criteria:
Met or exceeded owner or client needs
Applied project management techniques in an original way
Advanced the technical aspects and image of project management
Project of the Year for 2014: Vita-Mix Germany eShop
Outstanding timeline performance to satisfy a business need
Used a combination of Waterfall and Agile to meet the schedule
5. 5
(1) Background of Vita-Mix
Vita-Mix
Cleveland-based kitchen products company since 1921
Today: premium blending equipment for home and business
High growth from healthy eating trend, and “foodies”
Organization including IT has high growth (new staff)
Growing overseas, focus on “Tier 1” countries (high income)
Marketing Strategy
Retail Partners
Online with www.vitamix.com, and some country-specific sites
Country-specific sites
Vita-Mix IT capacity sets pace for country site development
6. 6
(2) Background of Germany eShop
Plan “A” for marketing to Germany, as of Fall of 2013
Continue recruiting retailers through 2013 and 2014
IT: deploy German eShop in later 2014 (after UK, Ireland)
Management: German eShop in late 2014 is unacceptable
7. 7
(2) Background of Germany eShop
Plan “B” for marketing to Germany, on December 2, 2013
…
Vita-Mix IT teams remains on UK, Ireland web sites
Find IT subcontractor and deploy German eShop in 2014 Q1
Note “Ambiente” trade show in February 2014, so…..
Target: deploy temporary eShop by January 31, 2014
Timeline of 2 months is half of typical German eShop project.
8. 8
(3) Project Scope
Germany eShop, firm scope
eShop dedicated to German market
Offer (18) items: blenders, accessories, cookbooks
German language products exist, for retail
Purchase using shopping cart and credit card
Comply with strict German laws for consumer data privacy
Web site content and documents in German
Communicate with customers and Vita-Mix systems
13. 13
Agenda
1) Background of Vita-Mix
2) Background of Germany eShop
3) Project Scope
4) Project Team and Partners
5) Project Methodology (*)
6) Project Timeline
7) Project Tools
8) Timeline Reduction (*)
9) Project Success Factors & Lessons Learned
10) Closing
who, what, why
how and when
(*) Take-aways for Project Managers:
(5) Project Methodology - hybrid
(8) Timeline Reduction
(--) Overseas project items
14. 14
(5) Project Methodology
Choose: Agile, Waterfall, or Hybrid ?
Factors:
Limited shared team experience with Agile
Link: (4) Project Team
Short timeline (4 week core development time; 9 weeks total)
Agile
Not a good fit for a new process on short timeline
Fixed project scope makes re-prioritization unnecessary
15. 15
(5) Project Methodology
Choose: Agile, Waterfall, or Hybrid ?
Waterfall
Highly serialized (non-overlapping) phases poor for timeline
Web site requirements not complete until week 5 of 9 weeks
Waterfall style for this project must be heavily overlapped
16. 16
(5) Project Methodology
Choose: Agile, Waterfall, or Hybrid ? Use Hybrid:
This slide shows standardized
iteration structure & timing.
Vita-Mix eShop followed this
pattern loosely, with variation
in timing of subsections.
Return 8 (A) Progressive Elaboration
17. 17
(6) Project Timeline
Note dual critical paths for: (A) Systems, (B) Partner Setup
Week start: Dec 2 - Dec 9 - Dec 16 - Dec 23 - Dec 30 - Jan 6 - Jan 13 - Jan 20 - Jan 27 -
Week end: - Dec 6 - Dec 13 - Dec 20 - Dec 27 - Jan 3 - Jan 10 - Jan 17 - Jan 24 - Jan 31
Timeline for Systems
Reqmts & Page Layouts Create, Approve
Design Site Processing Data privacy; Inventory; shopping cart with pricing, tax
Backoffice Order processing; warehouse; shipping
Product Products Products, categories, pricing
Content Translate Translate Load Update
Legal Site legal notices Wrrty; Privacy; Terms Translate Load
Email templates Order conf; Ship Translate Load
US Site Integrate US/DE Link to/from US site (repair shops); "imprint"Load
Backoffice Order process Analysis (banking, order coding) Setup Test Load Prod
Shipping Analysis (warehouse; shipping) Setup Test Load Prod
Testing Approve, Test Parallel with development Integrate Approve
eShop Platform Setup: Magento, PayOne, Concardis Load Prod Approve Go
Page content Categories, Products, Legal Load Prod Approve Go
Processing Inventory; order; tax; ship; emails Load Prod Approve Go
Timeline for Partner Setup
Acquire Vita-Mix tasks Identify Partners Negotiate contracts; make administrative setups
Partners Legal work Negotiate contracts with four new vendors
New D&B (IT) Ltr of Und Contract (phased payment, penalties)
Partners PayOne (credit) Contract (fee issues; admin setup)
Concardis (pay) Contract (banking lag issue; admin setup)
DomFact (host) Interim via D&B Contract (Privacy)
Holidays
(A)
(B)
Jan29
18. 18
(6) Project Timeline
Critical Path: (A) Systems work – weeks 1 to 7
Week start: Dec 2 - Dec 9 - Dec 16 - Dec 23 - Dec 30 - Jan 6 - Jan 13 -
Week end: - Dec 6 - Dec 13 - Dec 20 - Dec 27 - Jan 3 - Jan 10 - Jan 17
Timeline for Systems
Reqmts & Page Layouts Create, Approve
Design Site Processing Data privacy; Inventory; shopping cart with pricing, tax
Backoffice Order processing; warehouse; shipping
Product Products Products, categories, pricing
Content Translate Translate Load Update
Legal Site legal notices Wrrty; Privacy; Terms Translate Load
Email templates Order conf; Ship Translate Load
US Site Integrate US/DE Link to/from US site (repair shops); "imprint"Load
Backoffice Order process Analysis (banking, order coding) Setup Test
Shipping Analysis (warehouse; shipping) Setup Test
Testing Approve, Test Parallel with development Integrate
eShop Platform Setup: Magento, PayOne, Concardis Load Prod
Page content Categories, Products, Legal Load Prod
Processing Inventory; order; tax; ship; emails Load Prod
Holidays
Overseas project notes: translation issues; “imprint”; navigation notifications
19. 19
(6) Project Timeline
Critical Path: (B) Partner Setup – weeks 1 to 7
Week start: Dec 2 - Dec 9 - Dec 16 - Dec 23 - Dec 30 - Jan 6 - Jan 13 -
Week end: - Dec 6 - Dec 13 - Dec 20 - Dec 27 - Jan 3 - Jan 10 - Jan 17
Timeline for Partner Setup
Acquire Vita-Mix tasks Identify Partners Negotiate contracts; make administrative setups
Partners Legal work Negotiate contracts with four new vendors
New D&B (IT) Ltr of Und Contract (phased payment, penalties)
Partners PayOne (credit) Contract (fee issues; admin setup)
Concardis (pay) Contract (banking lag issue; admin setup)
DomFact (host) Interim via D&B Cont (Priv)
Holidays
Overseas project note: most vendor paperwork was in German (standard
contracts, pricing lists, Service Level agreements).
20. 20
(7) Project Tools
Project documents: Vita-Mix sharepoint site
Typical core project documents, in MS-Word, MS-Excel
Schedule.xls; Risk/Issue/Action.xls; Requirements.doc
Technical Development: “Magento” eShop platform
WiTopia software for German IP address simulation
Bug-tracking: Mantis internet-based tool (D&B standard)
21. 21
(8) Timeline Reduction
Timeline Reduction Methods Used in eShop project
Team used a collection of timeline reduction methods
Nothing revolutionary, just a constant focus on timeline
Types:
(A) Compress Waterfall Plus Agile
(B) Minimize Deliverables
(C) Minimize Time Delays
22. 22
(8) Timeline Reduction
(A) Compress Waterfall Plus Agile
…
Fast-tracking = compress by overlapped phases (in parallel)
Shortens timeline, increases risk of errors and rework
Agile techniques to reduce risk:
Empowered self-organizing teams
Address issues without time for management involvement
Minimal formal expectations, only a weekly status
Daily team meetings
Status 8:30-9:00am EST: core Vita-Mix and D&B (IT)
Minimal time lost (1 day) if go off-course.
23. 23
(8) Timeline Reduction
(A) Compress Waterfall Plus Agile (continued)
…
Progressive Elaboration (hybrid: red, green, blue, yellow)
Define requirements overall at high level as framework
Define requirements and develop sections progressively
Link: (5) Methodology: Hybrid
Frequent direct collaboration, light documentation
Ex: for requirements session for function “X”
Include all voices and decision-makers in one session
Goal: define and approve requirements in one session
Early and frequent testing and validation
Informal validation of IT WIP during daily meeting
Perform at least pre-test for each function as available.
24. 24
(8) Timeline Reduction
(B) Minimize Deliverables
…
Focus on “external” or “required” deliverables
Minimize “internal” team deliverables
Example:
Select team members with needed skills (avoid training)
The Lead BA on the project was web specialist
BA work needed on Ordering and Shipping in VMix systems
BA for Order processing, for analysis & accounting setup
BA for Shipping, for analysis and system setup.
25. 25
(8) Timeline Reduction
(B) Minimize Deliverables (continued)
…
Examples (continued)
Use known/proven tools (avoid learning curve, integration time)
Magento/PayOne/Concardis were proven integrated tools
PayOne chosen over Chase, to avoid technical integration
German law firm as proxy for Vita-Mix (eliminate translations)
German attorney summarized German documents for US
Redlining was done directly in German documents
Use partners with existing relationships (mutual knowledge)
Use partners who know each other and ready to start work.
26. 26
(8) Timeline Reduction
(C) Minimize time delays
…
Use backups for critical path resources
Martin Bielke (account manager at PayOne) out for holidays
Bielke found backup resource to continue PayOne, Concardis
Use partners with existing relationships (mutual trust)
D&B with Letter of Understanding (with unknown Vita-mix)
Existing relationship of D&B and K&H was incentive for D&B
Relax standards to reduce wait time
Vita-Mix marketing allowed use of “pasted” logo file
Vita-Mix finance allowed Payone, Concardis (not Chase).
27. 27
Agenda
1) Background of Vita-Mix
2) Background of Germany eShop
3) Project Scope
4) Project Team and Partners
5) Project Methodology (*)
6) Project Timeline
7) Project Tools
8) Timeline Reduction (*)
9) Project Success Factors & Lessons Learned
10) Closing
who, what, why
how and when
conclusion
(*) Take-aways for Project Managers:
(5) Project Methodology - hybrid
(8) Timeline Reduction
(--) Overseas project items
28. 28
(9) Project Success Factors & Lessons Learned
Project Success Factors
Clear scope and priority provided focus
Decision criteria usually simple: what is fastest option?
Strong sponsors (IT and marketing)
Provided resources: international staff, multiple BA
Resources available as needed, full-time or otherwise
All team members were experts in their role
Tight timeline forced cooperation and trust and focus
Existing Vitamix.com provided scope example
29. 29
(9) Project Success Factors & Lessons Learned
Project Lessons Learned
High cost of specialty legal services; minimal budget planning
Get estimates earlier at least as FYI (large legal expense)
Translation (and all project deliverables) should be validated
Allow time for validation
Get internet-based project document site for access by all
The Vita-Mix based site required document coordination
Contract negotiation with D&B – ran long; posed a risk
Mitigated by D&B incentives with partnership with K&H
Introduce BZ:
BZ = IT and PMO as contract and perm around NEO
Contracted through LR Solutions at Vita-Mix; hired for ERP, switched to eShop
BZ now at E&Y
PRESENTATION =
One slide on PMINEO awards
Main presentation = Vita-Mix
Q&A –
light during presentation; Q&A time at end.
Slides –
Slides will be posted to PMINEO site for this calendar meeting (yes?)
PMINEO annual awards for
outstanding PM professional
outstanding project
Timing
20 minutes:
light intro, awards, agenda
bulk of time on items (1) – (4)
40 minutes:
Bulk of time on items (5) – (8)
5 mins or less on (9)
15 minutes
(10) Q&A
NOTE: take-aways --- “What is in it for me ? “
(5)
(8)
(--)
Items (1) – (4) = who, what, why
Later:
Items (5) – (8) = how and when
Items (9) – (10) = Conclusion
.
Vita-Mix
Cleveland company since 1921, first with general kitchen products; Barnard family
Added blenders in 1937
Product line now is premium blending equipment for commercial and home use
Home units in USA
$250 “personal”, competes with Nutri-bullet
$700 top-end multi-function (mix, make dough, heat soup, make ice cream)
Global Expansion
Vita-Mix has grown dramatically in recent years, in USA and now overseas
Appeal based on healthy eating, “foodies” (ex: Food Network) and other factors
Marketing analysis for “premium” blender; identified “Tier 1” countries (income)
Tier 1 examples: Canada, UK, Ireland, Germany…..
Marketing
Retail partners
Online marketing, with dedicated sites for top countries
Online sites normally through Vita-Mix IT teams
Capacity limits of Vita-Mix web team and infrastructure team created extended pipeline and waiting period for Germany eShop
Vita-Mix was partnering with German retailers; supplying them with German-branded products through UK warehouse.
Vita-Mix management requested eShop for Germany asap to combine with retailer efforts.
IT pipeline constraint –
IT/management discussed options for re-arranging pipeline of per-country projects
Management wanted German acceleration without delay of others…not possible with Vita-Mix team constraints.
So…..
Vita-Mix web team must remain on course for UK, Ireland web site work.
Germany site must be through subcontracted IT, on hosted infrastructure. Can be temporary site
Ambiente: From 2016 site:
“Leading international trade fair for consumer goods.”
“Here is where the world meets up. More than 134,000 trade visitors from over 150 countries put together their core and supplementary product assortments for the coming year at the Dining, Giving and Living areas. ….. Ambiente brings business partners, ideas and success together at one location.”
German legal group and German IT group independently of each other noted that typical eShop project like this would require 4 months or longer.
Legal and IT partners resisted 2 month timeline at first, then agreed after adjusting other work and staff
2014 eShop was intended to be temporary solution
Replaced by eShop on Vita-Mix systems in early 2015
Comply with strict German laws for consumer rights
NOTE: “Opt-in” for use of personal information
Data privacy laws in Europe are different from USA; ex:
Ex: Some private data requires “opt-in” (user positive acceptance)
Penalties can be harsh, including personal punishment
LITE - General site page navigation:
View “categories”
From a “category” select a unit to see detail page
LITE - General site page navigation (continued)
From a detail page, add to shopping cart
From shopping cart, enter/validate address; enter/approve credit card.
German marketing/legal: Avoid implied warranty in text.
German legal firm noted that German law is more strict than US law about marketing text and implied warranty.
Attorneys recommended that Vita-Mix “tone down” the US-based text anywhere that a statement could be interpreted as a statement of warranty.
HIGH LEVEL FUNCTIONAL DIAGRAM
Browse Categories, Products
(18) items: blenders, cookbooks, accessories
Use Shopping Cart
Add items, pricing to cart
Confirm inventory
Apply tax, shipping cost
PayOne
Validate credit card and amount
Validate address
Create Approved Orders
Send ordering email to consumer
Send order data to Vita-Mix backoffice systems
Pay Approved Orders
7-day lag for payment (originally proposed 30 day, for new vendor; 7-day to avoid buy/return issues)
Concardis
Process payment, to Deutschebank
Deutschebank access by Vita-Mix
Reference
Legal documents: Warranty , Data Privacy, Terms & Conditions
Email templates
Platform
Magento eShop Platform; Interfaces to PayOne, Concardis
Hosting on DomainFactory
Create Shipment data
Delivery promised within 2 weeks
Send shipment notification email to consumer
Send shipment instructions to UK Warehouse
Ship goods to consumer
As of December 2013, because of existing work with Germain retailers, Vita-Mix had:
German legal partner: Morrison Foerster
German marketing partner: Klenck & Hoursh
IT partner search
Some leads from Vita-Mix IT, ex: CIO contact -
OPTIONS NOT USED: Some generic industry template options, with various implementors (ex: Shopify, Magento, others)
K&H recommended D&B
Selection of D&B based on recommendation of trusted partner K&H, and existing working relationship with K&H (D&B will be more “invested”)
D&B recommended PayOne & Concardis as proven technical interface options
D&B recommended DF as proven working platform; was able to accelerate dev & deploy
NOTE: contract/temp/new employees – learning curve if uncommon methodology
Items (1) – (4) = who, what, why
Items (5) – (8) = how and when
Later:
Items (9) – (10) = Conclusion
.
TEAMS:
Vita-Mix (Roles: PM, BA, QA, business/legal)
Many newer or contracted resources with limited shared experience
Vita-Mix IT PMO and project processes in early stages
Set of project document templates; some usage
Waterfall style process
D&B (Development)
did have variety of methodology experience, but not with Vita-Mix
TIMELINE: Short timeline did not allow:
development of processes
execution of more than iterations (4 weeks core dev)
AGILE: No. Due to:
Limitations above
Reprioritization is a key benefit of agile, but of minimal help here……due to fixed scope
Serialized too long.
Requirements by week 5 – does not leave time for development, load, validate….
Hybrid
Chose simplified compressed waterfall, with milestones
Teams/subteams familiar with waterfall
Teams/subteams have limited experience working together
Hybrid was used with loosely iterative sub-cycles
Hybrid slide shows iterative style used at Progressive and EY:
Iterative sub-cycles are used in staggered timing
Traditional roles still used (BA, Dev, QA)
Unlike “Scrum” where all functions and roles are combined in each “sprint”
German eShop
Followed this hybrid style conceptually, without formal iterations.
Work was completed in logical subsections, with BA, Dev, QA in succession
Formal full integrated testing was completed at the end
See timeline across top: (9) weeks total, including holiday period
See major/minor columns down left
Two Critical Paths (A) and (B) will be detailed on next slides
Major overlap weeks 3 to 7
Target deployment: January 31; actual deployment January 29
NEXT: focus on (A) then (B)
CRITICAL PATH: Systems
Requmts & Design: (Marketing, WebBA, International business)
Product Content (Marketing, International business)
Legal (US legal; German legal)
US Site
Backoffice: (two specialized BA to analyze and define setup for accounting)
Testing: (lead QA with project team) normally pre-test functions as available
eShop: (D&B)
Overseas project notes:
Translations required rework to achieve everyday German language flow
“imprint” (corporate officer contact information) required
Navigation notifications to user needed between US/German-hosted sites
CRITICAL PATH: Partner Setup (legal and administrative setup)
Acquire partner
New partner:
D&B (contract issues on penalties, payments)
PayOne and Concardis (Vita-Mix finance wanted Chase; exception OK for timing)
DomainFactory (time required to resolve data privacy terms in contract)
Project site
Directly accessible only by Vita-Mix; needed coordination to send latest masters to partners
Used a collection of a dozen or so timeline reducers.
Nothing revolutionary, just constant focus on timeline.
Grouped as:
(A)
Overall methodology: use compressed waterfall, with traditionally “Agile” techniques to reduce risk from overlapped phases
(B)
Eliminate tasks where possible
(C)
Eliminate wait times where possible.
Define:
Fast-tracking = compress by overlapping work (in parallel)
(Not: Crashing = adding resources on critical path)
This project timeline relied heavily on fast-tracking; much work was in parallel
Risk:
Overlapping phases and tasks increases risk of errors and rework
Example: change in requirements requires rework of development
Use some Agile techniques
COMMENT RE: “AGILE” techniques – some people would argue these techniques are not only Agile
Progressive Elaboration
Recall hybrid: main framework of functionality, then subsections (red, green….)
Frequent direct collaboration, light documentation
COMMENT: If multiple versions in succession were needed to create a document….. could it have been done in one cycle?
Early and frequent testing and validation…. Possibly while function X is in progress
Define:
“External” deliverables = produced for users; probably “required”
“Internal” deliverables = used by team; may not be “required”
>> Look at tasks that are not external deliverables to user.
>> Can any be eliminated?
EXAMPLE:
Select team members with needed skills;
Primary BA was web expert, and “lead” BA
Second BA (SME) added to analyze and set up order processing in VM systems
Third BA (SME) added to analyze and set up shipment processing in VM systems
>> Training of team members during a project extends the timeline
Use known/proven tools.
Ex: eShop platform and integrations with credit card processors PayOne and ConC.
The “Magento” platform ready with “PayOne” and “Concardis” interfaces.
Vita-Mix Finance group preferred standard provider Chase Paymentech; but Magento/PO/ConC approach with proven interfaces was needed for timeline
Terms were less favorable than with Chase, but Chase terms were used to negotiate better fees and lag times with PayOne and Concardis.
>> Setup of new interfaces to use Chase was extra work that was avoided
German law firm functioned as trusted proxy for Vita-Mix
Most legal documents for project were in German language
Slow path would have been:
Translate to English > US review in English > Redline > Translate to German
Chosen path:
Vita-Mix had a client/attorney relationship with German attorneys
German attorneys review German docs > Recommend revisions > Make redlines in german documents directly
>> Translation and re-translation of legal docs was avoided
Use partners with existing relationships
Partners know each other; ready to “go to work” immediately
>> Partner selection was influenced in favor of ready-to-work relationships
Use backups for critical path resources
PayOne: team working with Martin Bielke of PayOne; note long lead time for contract and then (30 days) account setup, and Bielke holiday schedule.
Bielke found delegate to keep processing over holidays
Use partners with existing relationships
D&B worked with LOU, not contract, for bulk of project.
Relationships, not contract penalties, were major motivation
Avoided delay of contract negotiation
Relaxation of some standards
Marketing Director agreed to non-standard details such as “pasted” not “constructed” Vita-Mix logo file
Vita-Mix finance wanted Chase Paymentech, not PayOne & Concardis. Chase setup time was too long for project timeline, so, exception allowed.
Items (1) – (4) = who, what, why
Items (5) – (8) = how and when
Items (9) – (10) = Conclusion
Take-aways for Project Managers – (WIIFM – What’s in it for me ? )
(5)
(8)
(--)
.
Scope and priority and timeline
Triple constraint >>> focus on timeline, maintain scope. Easy decisions.
Strong sponsors
Resources
All team members were experts in their role
“role” meaning project function, and other specifics (ex: German law and implied warranties in marketing text)
Tight timeline
Budget and Legal
There was not a pre-conceived budget; expenses were approved as needed
Legal costs of this type are VERY high (experts in German/foreign sites and related issues for data privacy and otherwise; also bi-lingual).
Cost status and estimate was not made until second half of project.
Any Vita-Mix staff not familiar with international costs were very surprised (some yes, some no)
Translation
Team assumed that translations would be ready to use; required “everyday” update
Extrapolate: all work needs to be “validated” or tested somehow
Project site
Doc site with masters accessible to Vita-Mix staff
Required VM staff to coordinate doc copies with non-VM staff
Contract negotiation with D&B
Ran long; some project risk if contract not reached.
D&B (IT) relationship with K&H (marketing) provided added incentive to succeed