1 of 22

Project management: Strategy is everything!

Published July 25, 2019�Presented as part of the Marketing Academy and organized by the Enterprise Marketing Hub

.Communications Camp 2019.

.July 25, 11:10–11:55 a.m..

2 of 22

A little about me.

Jennifer Jones, DMA, SPOC, SMC�EdPlus Project Management

I am a project manager with EdPlus at Arizona State University. I work directly with the creative and Salesforce development teams and focus on coordinating web development, design and print projects. Assets include ASU Online, EdPlus, Earned Admissions, Continuing Professional Education and corporate partnerships, including Uber and Starbucks.

I also have a Doctor of Musical Arts degree in vocal performance, and I sing with Arizona Opera when I am not managing projects.

Agile certifications: �SCRUM Product Owner�SCRUM Master

Insert a photo here

3 of 22

What is Scrum?

What is a Sprint?

We use two week sprints at EdPlus. A sprint is a time-boxed period of time that the team agrees upon to deliver a component, project, or deliverable.

Each team also participates in two stand-ups each week (between 15-30 minutes in length).

The goal of the stand-up meeting is to give an update.

What have you been working on?
What are you working on today?
What’s in your way? (Any blockers?)
What do you need from other team members to move your work to complete?

Scrum is an Agile Methodology.

“One of the key characteristics of any project is the uncertainty of results or outcomes. It is impossible to guarantee project success at completion, irrespective of the size or complexity of a project. Considering this uncertainty of achieving success, Scrum attempts to start delivering results as early in the project as possible. This early delivery of results, and thereby value, provides an opportunity for reinvestment and proves the worth of the project to interested stakeholders.”

https://www.scrumstudy.com/

4 of 22

Agenda.

State of the queue
Challenges
Workflow
Jira
Calendar
Dashboards
Questions

5 of 22

State of the queue?

What is all of this stuff and. �.who is working on which part?.

6 of 22

.Where do I start?.

7 of 22

Challenge

.How can I organize this in a way � that will help the team?.

.Do multiple teams use this board?.

8 of 22

.Challenge accepted.

Goals

Quickly organize what is in the queue - (without disrupting the team)
Which tickets are projects?
How should I organize them?
Who is the lead for each area?
How do they want to assign work?
What step is next in the process?

9 of 22

Workflow

.How can we make sure. �.the next step happens?.

.What is the next step?.

10 of 22

.What is our internal process?.

Resources needed to create, update, or redesign a website:

Copywriter/content.
SEO.
UX/design.
Development.
Data layer.
Content and design Q/A.
Q/A and testing.
Development fixes all the things.
Launch.
Additional bug fixes.

11 of 22

Jira

.Project parents, linking tickets. �.and calendars, oh my!.

12 of 22

.Project parent tickets.

13 of 22

.Linking tickets.

Linking tickets to the project parent ticket assists our team in tracking each piece of the larger website deployment or redesign.

�This example is a snapshot of some of the tickets linked to a larger UberEats website launch.

14 of 22

Calendar (using project parent ticket due. � dates as launch window).

15 of 22

Prioritization.

Challenges

Multiple teams, multiple stakeholders
Scheduling work based on capacity, team resources and priority
Conflicting delivery dates/requests
Urgent requests
Keeping everyone in the loop
Adjusting timelines and deliverables quicky
Having a clear picture of the current status
Keeping an eye on delivery/launch dates

16 of 22

.How soon can we launch?.

Example A estimated timeline:

Design 6/14.
Dev 6/28.
Design/dev Q/A 7/3.
Additional dev edits 7/5.
Q/A 7/8–12.
Launch 7/15.

Example B estimated timeline:

Content and images 5/10.
Approval from London and PluS 5/17.
Design 5/24.
Design approval 5/28.
Final design edits 5/31.
Development 6/3–6/7.
Design and dev Q/A 6/10–6/12.
Final development edits 6/13–6/18.
Q/A 6/19–6/21.
Launch 6/24.

The importance of a good estimate: I have a very good friend who tells her clients, “Development is a discovery process, and as such can require additional troubleshooting, time and effort when needed.”

17 of 22

Other items of note

Importing Issues in Jira
Cloning tickets
Linking tickets
Moving tickets to another board
Tagging someone in comments
Making someone a watcher
Removing yourself as a watcher

18 of 22

Dashboards

.Presenting the right data to the right.� team … in the right format.

19 of 22

The power of dashboards in Jira.

Dashboards can be audience-specific
Display your filters in ways that suit the team and leadership
Create filters that help your teams find what they need quickly
Share filters and dashboards between teams and groups
A few examples:

20 of 22

.Questions?.

Where did you get these awesome kitten pics?

Kitten images from: pexels.com/search/kitten/

21 of 22

Takeaways

Jira — ASU Enterprise Software Solution: asudev.jira.com

Jira Software: atlassian.com/software/jira/features

22 of 22

Thank you

Do you have questions? Please feel free to email me at jennjones@asu.edu