How an Agile Tool Made Me Quit My Job

Full disclosure: While I have had some contacts with Targetprocess senior management, I am not affiliated, associated, authorized, endorsed by, or in any way officially connected with the company.

Here is the first part of my journey on becoming a Targetprocess advocate.

And really understanding why everything look like a nail when all you have is a hammer.

What is Targetprocess?

Targetprocess is a visual platform to help you adopt and scale agile across your enterprise. You can implement your own framework or use existing ones to achieve business agility and see the value flow through the entire organization.

How did it all start?

A few years ago I was an SAP consultant dreaming of transitioning eventually to Project Management. There were a few roadblocks however:

• I was (moderately) good at my job. And it is generally accepted that good (billable) consultants bring more value than project managers (PM) - hence are not ‘promoted’ to that position.

• I was (and still am) an introvert with questionable and at the time, unproven, leadership skills. Understand: not PM material.

Still, I had always loved resources management video games, and (real life) project management seemed like a lot of fun.

I started working on the technical skills I thought would help me achieve my dream despite my evident shortcomings: learning project management theory (by preparing the PMP), and learning about Agile. My strategy was simple. If I could not be a classic project manager, brimming with authority, I would be an Agile one: a facilitator, well versed in methodologies, tools and processes for team and delivery optimization.

What was the plan?

The plan was simple:

• Become a Scrum Master (The facilitator in the most popular agile methodology: scrum)

• Convince my company that we needed to transition to a more agile project management style

• Get my foot in one project as a scrum master / project manager

Getting certified took a week of intensive and very rewarding studies. For a moderate cost, I was a Professional Scrum Master (PSM), having passed the test. (Please not that there are two main organism that offer certifications for Scrum: Scrum Alliance and Scrum.org. I chose the latter as attendance to a workshop was not required).

Freshly certified Scrum Master, I thought of applying my knowledge on myself, managing my own tasks on a agile way. To do so, I needed a tool !

Targetprocess?

Not yet.

Without any particular experience, I went through the process of testing extensively a dozen of agile tools (including famous ones like Jira, Pivotal Tracker). My requirements were simple:

• Something easy to use

• Something cheap

The winner of my initial selection process was yodiz.

I started using the tool extensively and soon was able to build two prototypes:

• One that showcased how my company teams could manage their tasks in a kanban/agile way,

• One for our projects, by translating the SAP activate methodology in the tool.

Then, I decided to write a ‘white paper’ (or ‘white powerpoint’?) on agile project management for SAP projects using yodiz. In the process of creating the document, I eventually noticed that I was encountering limitations. I needed a more flexible tool.

My second selection process included more specific requirements (flexibility, integration with other tools, reporting capabilities), a higher budget, and more time for customizing. I retested tools that I had previously eliminated, and started to test some higher tier options. I initially thought I would select the right tool based on weighted criteria. But things were simpler than that.

I usually allocated 3h to customizing and testing one tool (Jira was initially the only tool to fully use the allocated time).

I understood I had a winner when I spent my whole weekend on one tool and didn't want to stop. I was not testing anymore. I had found what I was looking for.

Targetprocess?

Yes!

Why Targetprocess?

If you remember, I was still at the time a consultant, and a freshly certified scrum master. Targetprocess offered me an incredible flexibility to configure exactly anything I needed, combining my technical skills and my methodology knowledge.

The tool offered a free instance: unlimited in time and users, but limited in number of items that could be created (1000).

Once I decided on it, I played around for weeks, using all my free time to translate the SAP Activate Methodology in the tool.

Everything I had in mind materialized, and I didn’t have to compromise anything.

So, now what?

I believed so much in the tool and in the delivery model I had in mind that when my company didn’t totally understand the urgency and strategic importance of a more agile, visible and collaborative management style, I started looking for a new position. I knew exactly what I wanted to do, but was ready to take my time to get there.

I luckily got an interview with a great firm (Company B). Unbeknownst to me, company B had a challenge with the adoption of new tools and methodologies. On my second interview, as I was explaining why I wanted to quit my job, the partner in front of me had an aha moment. On my last interview, I took my computer out and presented Targetprocess to my manager to be, explaining what I wanted to do with it. I had just understood that it was what they were looking for.

What happens next?

I chose to work for Company B with only one goal in mind: Make the change happen. Transition the entire company to Targetprocess. See how agile work at company level: all projects managed in a central tool. All departments.

Visibility at company level… without having to actually meet/bother people (don’t forget, I was/am still an introvert…).

Did I succeed ? The story will continue in a future blog entry :)

Spoiler: I am now a Senior Project Manager Specialized in Agile Digital Transformation.