My Agile Journey

---

After college (University of Maryland Robert H. Smith School of Business, 2 Majors in 3.5 Years! ) I lacked the imagination to know what sort of career I wanted. I just knew I wanted a desk job.

I was hired by ADVO (Mail advertising) in early 2005 as a Microtargeter. I made demographic maps and reports to help retailers chose where to send their mail advertising. 

I learned: 

• Microsoft Excel (to think I thought I knew it before!)
• How to trick our ArcGIS mapping software into making the complex maps our retailers loved.
• How to elicit requirements from our Ad Sales Reps, so the materials I created would help land the sale.
• How to explain complex demographic calculations to non-technical audiences. 

After ADVO was acquired by Valassis (Newspaper advertising) in 2007 an effort began to integrate the two companies. I participated in a small cross-training effort, so as to build SMEs (Subject Matter Experts) with dual expertise. 

I learned:

•  Microsoft Access (to think I thought I knew it before!)
• How to look for steps in complicated processes that could be automated.
• How automation can reduce repetitive tasks and increase accuracy.
• How to make training materials that broke down complex procedures.

In 2008 Valassis began an effort to create software that could build Integrated and Optimized Media Plans to sell both Newspaper and Mail Advertisements to our expanded customer base. I joined the effort as a business SME. 

I learned:

• It takes more than just developers to build software.
• Seeing an idea come to life is energizing.
• Testing new software and working to eliminate defects is rewarding work.
• A team of motivated individuals (developers and business) working face to face on a daily basis can accomplish almost anything.

After the launch of the new  "IMO: Integrated Media Optimization" software, I was chosen to be the Adoption Manger. In this role I would help the organization transition to IMO and retire legacy systems.

I learned:

• Training people how to follow steps is different than helping them learn how to fully leverage a complex new system.
• How to identify enhancements worthy of developing from feedback.
• What you think your customers need and what they actually need are often different. 
• How to differentiate between a complicated user error, data integrity issue, and a system defect. 
• Techniques for communicating and coaching large teams through significant change. (The concept of tl;dr)

As IMO began to hit its stride, in 2013 I had the opportunity to explore other solutions to help automate processes for the large team of Marketing Analysts. 

I learned:

• How to code apps in Alteryx (deepening my appreciation for parameterized code and a well-crafted decision tree.)
• How to coordinate updates, releases, and installation to minimize downtime. 
• How to perform Proof of Concepts to test potential solutions.
• That I needed a fresh new challenge. 

My Game Changers:

• My first official mentor (Thank you Jim!)
• Permission to embrace writing in bullet points (people don't love reading long paragraphs anyway!) 
• Encouragement to reflect on what type of work I enjoy the most

In 2015 I began a job search, the first since I graduated college back in 2005.

I learned:

• I didn't know what the role I had been performing  was called to search for the right type of new job.
• My resume made me look like a Marketing expert not someone who could build software.
• My vocabulary was filled with jargon that made it difficult for people to understand my skills and what value I could bring.

In January 2016 I took a new role as a Systems Analyst at a technology funding company called TEDCO. It was kind of like working behind the scenes at Shark Tank. 

I learned:

• A lot of different problems can be solved with a well executed Excel or Access tool. 
• Keeping an ear out for problems to solve and being organized and determined enough to solve them will always help you add value. 
• What it's like to be a customer purchasing and implementing a SAAS solution.
• That most would refer to my experience building IMO as an Agile software development experience.
• Most companies go Agile by leveraging the Scrum framework. 
• I missed being on a team focused on building software.

My Game Changers:

• I read Jeff Sutherland's book, "Scrum the Art of Doing Twice the Work in Half the Time"
• I went to Scrum Alliance for training and received my CSM (Scrum Master) certification.
• I independently studied and received my PSPO (Professional Scrum Product Owner) certificate from Scrum. Org.
• I started practicing as many Agile habits as I could in my personal and professional life.
• I updated my resume to better articulate my skills and experiences in non-jargon.

In April 2017 I started at basys (Enterprise Benefits Administration Systems) as a Business Analyst on their Product team, I served the Product Owner role on an Agile Scrum Team. 

I learned:

• With a systematic approach I can quickly learn any new domain (not just marketing systems).
• All systems come down to rules engines and decision trees.
• Best Practices for release notes and customer sales demos.
• How to leverage parameterization to create a highly configurable SAAS system.
• I love turning around problematic projects. 
• How to layer in refreshed functionality over legacy systems to allow for iterative releases.
• That even a rough mock up can elicit more requirements than a blank piece of paper. 
• How to use Agile project software to organize Features, User Stories and Defects.
• Unaligned expectations between customers and businesses result in decreased employee morale.

My Game Changers: 

• I studied hard and earned my CBAP (Certified Business Analyst Professional) from IIBA (International Institute of Business Analysts) 
• I read Cal Newport's book, "Deep Work"

In late 2019 I started at 14 West as a Senior Business Analyst creating software to empower e-Markers to configure their online campaigns. 

I learned:

• Some companies utilize both Business Analysts and Product Owners on Scrum teams. 
• BDD Acceptance Criteria format.
• How to partner with an external UI/UX design team.
• Best  Practices  for promoting an Agile transformation; such as Agile Transformation. newsletters and Community of practice.
• Timing is everything. 

My Game Changers: 

• I read John Doerr's book, "Measure what Matters"
• I read Robert Cialdini's book "Influence, The Psychology of Persuasion"
• I read Dale Carnegie's book, "How to Win Friends & Influence People" 

In mid 2020 I started a role as a Consultant Product Owner at FINRA helping to create an improved online experience for filing FINRA and SEC forms.  

I learned:

• How to start a new position entirely remotely (thanks Covid).
• The increased value agendas and other planning tools in an entirely virtual environment.
• A well executed retrospective can be a game changer.
• The Federal hiring process is slow. 

In late 2020 I started a role as a Systems Analyst at a Federal Agency helping to redesign a legacy system. 

I learned:

• How to become a better Agile coach and mentor those less experienced around me.
• Techniques for Agile success when the Agile framework has been heavily adapted.
• The value of transparency among teams and all stakeholders.
• That best practices work.

My Game Changers: 

• I read John G. Miller's book, "QBQ! Question before the Questions" 
• I read Brene Brown's book, "Dare to Lead"
• I read Dr. Brinkman and Dr. Kirschner's book, "Dealing with People you can't stand; How to bring out the best in people at their worst"