Transforming SmartWood Solutions

Team members:
Under Guidance Of: ● Avadhanula Sarath(19030241030)
Dr. Mandaar Pande ● Mridul Mandal(19030241025)
● Swapnil Pagare(19030241028)
● Akhilesh Potdar(19030241030)
● Rasika Patil(19030241034)
● Yash Khelkar(19030241050)
“Design is not just what it looks like and feels like.
Design is how it works”.
- Steve Jobs
 Our Agenda
Success is walking from failure to failure.

1 2 3 4 5 6 7 8
About the What We Company Point Of How Customer
Persona View might We Empathy
Company offer Structure Journey Map
Yard Smart
 About
Company
● SMARTWOOD Solutions was founded in 2001 at Montreal
by Nic Carlson and Gig Carlson as a software development
company. SMARTWOOD Solutions started with a small
workforce of five-member team which comprised of two
developers and a technical support specialist along with Nic
and Gig.
Introduction ● SMARTWOOD solutions provides a Yard Management
System known as Smart Yard which optimizes and
coordinate and automates some of the yard activities.

Yard Smart 5
 What We Offer

Our Business Solution Provider BI Analytics Support

Launched in 2001, SMARTWOOD had For many of its users, Yard Providing analytical support to Support with customization
gained a strong reputation in its market, Smart was a vital part of a customers according to need
and its flagship product, Yard Smart, was yard’s daily operations.
used by several large companies and
located across the globe

Yard Smart 6
 Company
Structure
Administration Management
Project Manager

Sales Development Operations Support

Sales Team Team Lead Operations Manager Support Engineer

Yard Smart 7
 Meet The Team

Gig Pric
In Charge of sales In charge of all support
activities

Founder Developer

Nic Founder Support Specialist

Mayra
In charge of Technical
Development In charge of
Development team

Yard Smart 8
 Pain Points:
• First, the ability of SMARTWOOD to deliver Yard Smart to customers was hindered by manual
and error-prone steps ,the time required to build and release1 the application.
•  It was and there was no quick response regarding feedback. It was all quite laborious and
error-prone.  4
•  Technical staff had to stop working on other tasks to start the build procedure, validate, install &
delivery to customers .
3
•  Developers were also affected because they were unable to use SMARTWOOD Bug Tracker or
Visual SourceSafe during builds
•  release required several builds because quality assurance uncovered serious bugs. 2
•  inability of SMARTWOOD to accurately mimic customer environments to test and debug
issues. 
•  The overall delivery required time from SMARTWOOD staff as well as coordination with
customers. This was especially difficult since SMARTWOOD’s schedule and revenues
1
depended on the schedules of their customers, which varied. 
• The fourth issue was the intermittent unavailability of resources at SMARTWOOD.
• development and validation of Yard Smart was not continuous. Rather, there would be long
periods of development followed by intense testing “blitzes” as the release date loomed.
•  Developers had to go back to fix code that had been implemented weeks or months before,
often causing regression issues that made it difficult to stabilize a version toward the end of a
cycle.

Yard Smart
 Persona
Responsibilities- 

• Planning of the project and upcoming deliverables.

• Execution- Participate and execute planned deliverables.
• Time management- Match the time and cost tradeoff
• Budget-work for devising a budget for a project, and then sticking to it as
closely as possible.
• Maintenance-devise methods for properly supporting the final deliverable
going forward

Needs:
Rick Pattinson Stakeholders:
• DevOps CICD for seamless release of new versions of
Project Manager • Operations Team Lead smartyard software on customers' environments.
• Development Team • DevOps culture for better coordination between
• Implementation Team development team and operations team.
45 years of age, extensive experience of working Lead • Implementation of DevOps for Less time for feature
with the shipping industry of around 18 years. • Maintenance Team release.
Expertise in building and maintaining freight • DevOps will ensure Improved  support for already
tracking softwares. Earlier managed and delivered installed systems at client sites.
projects in similar industries. • DevOps project management tool for better tracking
bugs.
• DevOps Continuous Development tool for version
control.
Yard Smart • Onsite Devops support, implementation team from
vendor. 10
 Point of View:
User Need Insight

Operations Team Lead seamless release of new Majority of the time it is quite
versions of smartyard software painful to configure the client
on customers' environments. system/ environment according
to technical requirements.

Maintenance Team Lead After installation support It is not operationally feasible

to allocate technical resources
for after installation support

Project Manager Quick feature release Currently it takes 6-12 months

for release. Feature release
should be in less time as
customer needs should be
incorporated in the release
cycle.

Yard Smart
 How might we:

1 2 • How might we create and configure client-side

systems according to project requirements?

• How might we optimize technical team working

by eliminating extra responsibilities of
installation and maintenance at client side?

4 • How might we eliminate delay in feature

deployment in software development life cycle?
3

Yard Smart
 Customer Journey Map
Software Architecture Software maintenance/
Designing Software
Testing Support

Project Allocation
to YardSmart

Requirement
Gathering
Software Continuous
Software
Development Feedback
Deployment

Yard Smart
 Empathy Map Rick Pattinson
Job Role- Project Manager, Yard Smart

Says Thinks
• Development and production team are not coordinating • Think about quitting the job.
properly. • The struggle is getting harder day by day.
• Clients system/environment is complicated and causes •  Wants to solve these issues from the root. 
problems during the release. • Bigger and more successful the organization gets larger is the
• Can’t employ more staff to solve the issues.  issue.
• Needs better version control and documentation for
yardsmart.

Does Feels
• Manages teams that work in silos  • Uncertain.
• Struggles to deploy software to production.(takes a lot of • Anxious.
time.) • Stressed.
• Tries solving regression issues that made it difficult to • Frustrated.
stabilize a version • Worried.
• Tries to coordinate the development and production teams. • Stuck.
• Has quite a laborious and error-prone process. • overwhelmed.

Yard Smart
 Pain Points  Solution
Development and validation of Yard Smart was not continuous. Breaking the silos of development team and production team and
Rather, there would be long periods of development followed by implementing DevOps so as that development and operations of
intense testing “blitzes” as the release date loomed. SmartWood would happen continuously

The ability of SMARTWOOD to deliver Yard Smart to customers Reduce release lifecycle time and cost of the process so that we
was hindered by manual and error-prone steps ,the time required can deliver our product on time. Hence building a CICD pipeline
to build and release the application. between  smartwood and its clients to make realise fluid and
secure.

Technical staff had to stop working on other tasks to start the DevOps Continuous Deployment , which includes ,review , staging
build procedure, validate, install & delivery to customers . and Production solves this issue. 

Developers were also affected because they were unable to use Implementation of DevOps continuous planning and better tools
SMARTWOOD Bug Tracker or Visual SourceSafe during builds like Mantis Bug Tracker will solve this problem

Release required several builds because quality assurance Devops Continuous Integration , Which includes ,Build, Unit Tests ,
uncovered serious bugs. Integration tests. Will solve this problem

Inability of SMARTWOOD to accurately mimic customer Building a CI-CD pipeline between  development environment and
environments to test and debug issues.  Production Environment (Clients) Through a VPN connection will
eliminate this issue.

 Developers had to go back to fix code that had been Implementing Continuous development Version Control software
implemented weeks or months before, often causing regression Like Git. 
issues that made it difficult to stabilize a version toward the end
of a cycle.

 The fourth issue was the intermittent unavailability of resources Hiring a Vendor for implementing , maintaining DevOps in
at SMARTWOOD. organisation.  
 Summary
• Just like another enterprise software project , smartwoods project has 3 phases
Acquisition , coding, delivery.
• The majority of the problems smart wood has is in delivery.
This is because development and operations teams work in silos.
DevOps is the clear solution.
• Hence the rick the project manager has created a RFP for DevOps implementation.
Thanks