Clothes R Us
Essay by iimk • April 23, 2016 • Coursework • 942 Words (4 Pages) • 1,067 Views
Transcript of Clothes 'R' Us
Clothes 'R' Us
Clothes “R” Us - Company Evolution
Leading appareal retailer compnay in the United States
Between 1990 and 1997
Growth and financial success
Expanded its stores from 200 to 300
Almost doubled its employees
Revenue of ~$6.51 billion
Net earnings of ~$534 million
In 1998
Growth began to slow
In 2000
Expanded to more than 400 stores
Doubled its balance sheet debt
Program Chronology
Conclusion
Recommendations
Address warning signs when first noticed
Evaluate what issues occured and ways to address if happens again
Before making a decision, evaluate the costs vs. benefits
Create parallel work schedules
Consider dependencies
Work and communicate continuously with key people
Agile Software Development Methodology
System Design
Group 5:
Ronald Blanco
Anabel Fernandez
Ashley Fuchs
Stephanie Licea
Anabel Lopez
Plan
Product Definition and Architecture
Requirements
Design
Code
Test
Initial Deployment
Plan
Project Manager
Project Management Office
Weekly reports on project status
Spreadsheet with important metrics and ratios is prepared
by the PMO
Product Definition & Architecture
Requirements
Design
Code
Test
Initial Deployment
Details of the system objectives were thoroughly defined
Business Information Requirements
Technical Requirements
Operational Requirements
Architecture Team worked in data & software design
This phase was very successful due to the EMT's and
Project Managers' depth of experience with the business
Requirements
Clearly defined the objectives of the software for the system
Software Requirements
Functional & Conceptual Designs
User Interface Designs
System Interface Designs
Projects were scrutinized by various groups including:
Operations Steering Committee
Obstacles
Graphic User Interface (GUI) for the POS system
Planned to present the Committee in June
GUI was presented on the last week of June
Committee approved GUI 4 weeks later after numerous changes
The delay in the approval of the POS system GUI by the Operations Steering Committee resulted in delayed sign-off
for the credit application
Store Management
Custom development of a new store managment application
Adopt latest internet development tools
Modern, browser-based user interface
Easy integration with in store server
XML data transfer to stores
POS & Credit
Integrated POS and credit application had to interfere with store servers
Credit authorization was routed through the storer server directly to HQ
Private network connecting each store to HQ
Delay due to final requirements sign off
Program manager, Nord, bothered by product managers' lack of availability
Orlin wasn't aware of lack of focus on POS program
EMT was asked to investigate further
Four out of six product managers had submitted their resignations that day
build,
acquire, implement
Customer relations management
Four weeks behind schedule
Hardware had shipped from vendor earlier in the week
Hardware came with latest version of operating system
Development environment had used earlier version of operating system
Caused estimated delay completion of infrastructure project by four weeks
Allow store manager and regional operations manager to access their store's performance at any time
Implementation
...
...