The following guide is meant to provide a brief overview of CMD’s technical delivery process and some of the tools involved. In this guide we will cover a high-level view of how projects and executed by the Technical Services Group using Atlassian software and the various other software platforms and services that we use on a semi- regular basis.

1. Tools, Process &
Technical Delivery
at CMD

2. Overview
Using theguide to CMD’s technicaldelivery process.
Ramping Up
The
following guide is meant to provide a brief overview of CMD’s
technical delivery process and some of the tools involved.
In
this
guide we will cover a high-­‐level
view of how projects and executed
by the Technical Services
Group
using Atlassian software and the
various other software platforms and services that we use on a semi-­‐
regular basis.
We
will start
of by going over
the basics of Atlassian’s primary
project managment tool:
Jira.

3. The
Atlassian family of collaboration,
project managment and softwaretools.
Hipchat
Share
ideas
and
files
in
persistent
group,
video,
and
1-­‐on-­‐1
chats.
SourceTree
Harness
the
full
power
of
Git
and
Mercurial
in
a
beautifully
simple
application.
Bitbucket
Server
(Stash)
Manage
and
share
your
Git
repositories
to
build
and
ship
software,
as
a
team.
Confluence
One
place
for
your
team
to
share,
find,
collaborate,
and
get
more
work
done.
Jira
Issue
tracking
and
project
planning
to
collaborate,
build,
and
ship
great
products.

6. The 3 Pages You Need to Know
While Jira is a complex project managment tool,
thereare
ony 3
pages that you need to bereally familiar with.
The Dashboard
The
is your home screen in
jira and will show
everything relevant to you.
At
CMD
we have
different dashboards setup
for each department.
The Kanban Board
This is where you can see all the progress of all
projects currently being worked in
real
time.
Issues/Tasks
This is the page that shows what is going on with a
particular project.
Status,
specs,
stakeholders,
assets and progress are
all recorded here.

7. The Dashboard
Your homescreen in
Jira.
Producers
//
Producer
Dashboard
Program
Managers
//
Producer
Dashboard
Tech
Directors
//
TSG
Tech
Director
Dashboard
Developers
//
TSG
Developer
Dashboard
QA
Analysts
/
Proofreaders
//
QA
&
Proofing
Dashboard
Activity Overview
The
dashboard can be reached at any
time by clicking on the CMD
logo
in
the
upper left corner of any page in
Jira.
Here
you will see issues currently
assigned to you,
issues that you are
watching and a program-­‐level
snapshot
of work happening in
your department.
You
can load the dashboard for your
department by searching for one of the
dashboards listed to the right.

8. The Kanban Board
Here
is whereyou will find theup-­‐to-­‐the-­‐minutestatus
of everything currently being worked on.
Producers
//
PMO
Program-­‐Level
Board
Program
Managers
//
PMO
Program-­‐Level
Board
Tech
Directors
//
TSG
Program-­‐Level
Board
Developers
//
TSG
Program-­‐Level
Board
QA
Analysts
/
Proofreaders
//
TSG
Program-­‐Level
Board
Maintain Agile Efficiency
Kanban boards are
great for getting an
update on a lot
of projects fast.
Here
you can sort projects by client or
individual
stakeholder.
Using this board effectivly will prevent
projects from stalling and provide
current information on who is
overloaded and who has
availability.
Department
specific dashboards are
listed on the right.

9. 4
2
The Task/Issue View
Everything related to a project in
oneplace.
To
edits all available information on a
task,
click here.
This
is
where
you
will
see
all
parties
responsible
for
delivering
a
project
listed.
The
‘asignee’
is
the
person
who
currently
should
be
taking
action
at
any
given
time.
The
task
description
is
where
specs,
assets
and
any
other
informaion is
entered.
On
some
issues,
this
information
is
imported
from
Formstack.
Down
here
is
where
defects
and
bugs
will
be
listed
as
they
come
in
from
testing.
The
task (or issue)
level
is where you can
find the complete scope of information for
a project.
Every detail
and spec needs to be
listed here.
In
most projects the TD
will set
of the task once
assets are
nearly ready for
development.
For
projects involving emails
or QA,
a producer needs to fill out a
formstack which will automatically
generate a ticket with the relevant
information.
1
2
3
4
1
3

10. The Process
Going over
thesteps involved with builing out technicaldeliverables.
Moving Fast
In
the modern
era
of expanding IOT
innovation and multi-­‐platform
responsive design,
it is east for projects to get held up in
the
concepting phase while trying to find the best technical execution for
each project.
In
this section we will go over
some of the software platforms and
frameworks that the Technical Services
Group
uses to deploy
engaging,
responsive user experiences in
a fast and thorough
manner.
We
will start
off by talking about HTML
Email
development.

11. Email Development
The
following outlines theworkflow for HTML
email
development at CMD.
Formstack
Projects start
by producers erntering a
formstack for new email
projects that connects
to Jira’s API.
Litmus Testing
Once
emails
are
ready
for
testing,
they
are
checked
against
a
list
of
approved
email
clients
in
Litmus.
Jira
Jira
creates
a
task
that
is
assigned
to
a
Tech
Director
for
triage.
If
the
task
is
ready,
it
is
then
assigned
for
a
developer
to
build
out.
Deployment
Once
an
email
is
finished
testing,
it
is
deployed
through
an
email
marketing
manager
such
as
Mailchimp,
Silverpop or
Campaign
Monitor.

12. Banner Development
The
following outlines theworkflow for HTML5
banner development at CMD.
Jira
Projects start
by producers handing off a brief with
relevant specs to a Tech Director.
The
TD
will then fill out
a Jira task for the project and assign it to a developer.
Confluence
Once
emails
are
finished,
the
project
is
documented
in
Confluence
for
future
work.
Bitbucket Server
The
projects
is
built
out
by
a
developer
and
loaded
into
a
stash
repository
for
collaberation and
archiving.
Deployment
Once
an
email
is
finished
testing,
it
is
deployed
through
an
ad
server
such
as
Doubleclick,
Apple
iAd or
Facebook
for
Business.

13. Full Site Development
The
following outlines theworkflow for web
dev,
microsite &
eCommerce development at CMD.
Jira
Projects start
by producers handing off a brief
with relevant specs to a Tech Director.
The
TD
will then fill out a Jira task for the project and
assign it to a developer.
Confluence
Once
websites
are
finished,
the
project
is
documented
in
Confluence
for
future
work.
Bitbucket Server
The
projects
is
built
out
by
a
developer
and
immediatly loaded
into
a
stash
repository
for
collaberation and
revision
history.
Deployment
Once
a
website
is
finished
testing,
it
is
moved
from
our
local
test
server
to
it’s
permanent
hosting
environment.

14. Daily Standups
Working
with
the
different
groups
within
TSG.
Email Development Standup
TD:
Garrett
Gillas
//
9:30
am
Bobby
Pierce,
Richard
Jackson,
Alissa
Young
Jack
Meeks
Jeld-‑Wen Projects Standup
TDs:
Bill
Oliver
&
Tovar
Millhollin
//
10:30
am
Eric
Cutler,
Nathan
Marr,
Jeremy
Ingle
Sam
Averett
Other TSG Projects Standup
TD:
Russ
Hodgin
//
10:00
am
Erin
Albers,
Matt
Eggers
Vitaliy Hudz

15. THE END