4. your need our understanding of the need
> project “ArtCase” organized in 3 phases :
- phase 1:
• launch on Sosh.fr through a corner on their accessories shop
• a personalization module to integrate into the Sosh customer journey
• planning forecast : November 2012
- phase 2:
• Artcase standalone site for France with customer journey from A to Z
• planning forecast : Q1 2013 1st launch on Sosh.fr, then Artcase standalone site
- phase 3:
• replication of Artcase standalone site for Q4 2012 Q1 2013
France in OK and Spain. Corner Artcase on SOSH accessories
• all sites must be optimized for tablets shop
Totally integrated into the Sosh customer journey.
Exclusive artists on Sosh.
> constraints : Artcase.com eShop (FR
then UK tbc)
- design, customer experience and visual design •Standalone eshop
•Cross link with Orange Shop
will be done by a web agency
Mid term opportunity
- furniture of templates, zoning and PSD ArtCase corner on
Orange accessories
eshop?
10 interne France Télécom - Orange
4/26
5. your need the goals
> accessible and intuitive
> full functional coverage : content management, catalog and
products management, customer spaces, order management, ...
> exchange security
- compliance with norms and standards, best practices, …
- lock access between servers
> ability to interface with your information system
> scalable solution to internal processes
> reduce your internal load and increase your Marketing chances
> respect of project schedule
5/26
7. Project methodology A team working with agile software development methods
> Sequence of a release (version x.0)
Sprint 0
Sprint 1 Sprint 2 Sprint n End
Initiation
> Project organized in sprint steps
Initiating made by Product Owner :
• Defining features embedded in sprints : Product Backlog (to do list)
• Defining priority tasks (user stories)
Evaluating made by the project team:
• Evaluating tasks duration (planning poker)
• Evaluating criteria defining the end of tasks
• Building the Sprint Backlog (To do list for each sprint)
End of each sprint (Sprint review) :
• Showing work done through a demo and delivery for CIO
• Reporting problems
• Taking into account CIO feedbacks (bugs, changes)
7/26
8. Project methodology A team working with agile software development methods
> Tools for agile software development
The Product Backlog shows the entire to do list (user stories)
• some are well defined (forthcoming sprint)
• Other need to be reviewed
Reporting
• Burn-up (or Burn-down) chart showing process
> Project steering process
For each sprint review :
• Suggest features included for each sprint : Product Backlog
(To Do List)
• Defining To do List (user stories)
8/26
10. Project methodology Initiating
> Kick-off meeting
Team presentations
First roadmap with macro-planning
> Team organization
Building core team and secondary teams
Implementing project reports & reviews
Development & integration platforms
Tools for reviews
> Quality process
Project Management Plan
Risk & compliancy monitoring
Indicators
10/26
11. Project methodology Roadmap
> Roadmap is a key document started during the project initiation meeting
> Roadmap lists the To Do list, the following items :
Tasks and actions
List of priority
Continuous activities (corrective maintenance, support, steering,…)
Complet planning – tasks done by IT&L@bs and stakeholder, project steps
> Roadmap includes :
MS-Project planning includes the entire list of activities, materials, profiles and reliance
Budget dash board showing
Workload used and wahr remains to be done,
Several indicators for project governance
11/26
12. Project methodology Risk management
> Identifying risks
id Identify
Level
Probality of occurrence
List actions done to reduce risks Estimate Periodic
-
re-estimate iteration
trends
Defining and updating
> Recognization of probems actions to reduce risks
occured et and impact
Follow efficiency
analysis on risks in progress of actions
> Monitoring risk and actions
done during the project Close risks
committee.
12/26
13. Project methodology Service level management – indicators
> Quality of service is analyzed using indicators defined during
initialization phase and tracked in reporting
> Indicators evolves depending on project needs & project progress
> Indicators are calculated at least monthly and analyzed during the
Steering Committee
> Indicators are used by IT&L@bs to highlight through Dashboard
the quality of service provided on the project
13/26
14. Project methodology Global steering process
> Steering process Steering Committee
Steering committee
Project committee Steering
Progress meeting
Coordination, monitoring
(action plan, indicators)
Planning
> Risks management
> Planning management Project Project
Manager Committee
Synthesis Production
> Gestion des écarts Visibility on delivery Documentation,
Risk Management monitoring
Decisions & actions Project communication
Planning
Project team
14/26
15. Process Identify project steps
Step 1
Initiation
Staffing / Quality process
Risks / requirements
Features Step 2
Step 3
specifications / design Step 4
Integration/ Step 5
Development Acceptance /
Workshop Delivery Deployment / support
Setting Magento Go live
Specifications
Delivery and
Technical Graphic charter Acceptance platform
Production
Architecture integration deployment
deployment
Document
Custom Internal acceptance Operational
developement
qualification
Web design
Client acceptance
Documentations support Go live support
Validation / tests
document
Steering and Quality process management
15/26
17. our approach why Magento ?
> an industrialized and recognized solution in the market of e-commerce
software
- efficient and respectful of standards (security, architecture, ...)
- a vibrant community,
- popular solution that facilitates the recovery of activity in-house or by
a third party.
> an open source software foundation scalable and interoperable
- open source that allows own customizations to evolve,
- integration capability with significant third-party products (via web
services or connectors and Magento internal API).
17/26
19. our approach methodology and experience appropriate to large project scope
> experience
- IT&L@bs has real experience on large projects that require :
• to interface and work with other supplier companies
• organize the site into production in line with the overall project schedule
> approach with Quality Assurance (CMMI 3)
- monitoring of a quality permits :
• well reference the different actors and roles
• better track and follow the requirements for the project and its processes
(via the project dashboard)
• track and share risks
• optimize actions definition and implementation
19/26