Ch-ch-ch-ch-changes

Ch-ch-ch-ch-changes
Turn and face the strange

                 – David Bowie, “Changes”

Changes they are a happening!

After 13 years at Valpak (all working for the same man, I might add), I have resigned my position as Senior Director of Enterprise Agility.  It’s been a good ride but now I must move on. My work there is done and there is not much more I can do for Valpak, nor Valpak can do for me.  Beginning January 22nd, I will be joining Catalina Marketing as the Executive Director – Global Head of Enterprise Agility & Delivery Excellence.  I’m excited about the future but, for someone who specializes in adapting to change for a living, change has always been hard for me personally.

Three other changes to mention that aren’t quite as dramatic as the first.

  • I ended my stint on the Agile Alliance board after serving a 3-year term.  It was an experience of a lifetime that took me all over the world working with many different people on all things agile.  I will always be grateful for that experience.  With baby on board now and his Hydrocephalus condition (I know, a whole other blog post unto itself), the travel commitments were just too much.  However, even though my time on the board has come to an end, my service to the Agile Alliance has not.  I’ve been asked to serve on the Conference Steering Committee where I can best represent the OnAgile virtual conference which has been my baby from my time on the board.
  • I’ll continue to serve on the executive committee of the Tampa Bay Tech board (previously Tampa Bay Technology Forum).  However, this year I’m stepping up as Community Committee Chair (last year I was Co-Chair).  I’ll be joined by the very driven Gina Volmuth of The Praxsys Group as Co-Chair.  This year, we’ll be focused on continuing to grow the Tampa Bay Tech Meetup Pro, a co-op of almost 50 tech user groups comprising almost 15,000 unique members, as well as some exciting D&I initiatives.
  • Last but not least, my partner in crime on Tampa Bay Agile has changed.  Ryan Dorrell retired as co-organizer and Becky Hartman graciously stepped up to help me out.  Ryan will be greatly missed!  Together, him and I (along with a slew of sub-group event organizers, volunteer presenters, and generous sponsors) grew the group from less than 100 people about five years ago to almost 2,300 members today and one of the largest and most active tech Meetups in the Tampa Bay area.  Last year Tampa Bay Agile was named “Meetup of the Year” at the 2017 Tampa Bay Tech Awards.

 

Advertisements

6 Years Agile Strong at Valpak: It’s Been Epic!

Today marks the 6th agile anniversary here at Valpak.  Six years ago on October 14th, 2011 we set out on our first sprint.  Since then, we have lathered, rinsed, and repeated the agile way for a whopping 142 sprints.  The transformation was complete a long time ago but the journey never ends.  Along the way, we’ve had good times where we thought we could accomplish anything and we delivered extraordinary value to the business.  On the flip side, we’ve had bad times where we felt so inundated with stories and tasks that we thought we couldn’t possibly get anything done.  We’ve had teams that have been together from the start and teams that have come and gone.  We’ve had teams go from Scrum to Kanban and back again and vice versa in their quest for high-performance.  We’ve conquered massive epics and nailed the art of the quick hit.  We’ve put up boards and taken down boards (and have the paper cuts and Sharpie stains to prove it).  We’ve retro’ed so much that we probably know too much about one another … too, too much.  We’ve openly shared our agile story and hosted agile tours for over 50 companies from all over Tampa Bay and beyond.  It’s been epic!

But, all this wouldn’t have been possible without the craftsmanship, pride, and heart (a whole lot of heart) of our people (not resources, but people); the people on our teams that work tirelessly sprint after sprint and story after story to deliver something that amazes our Product Owners, our stakeholders, and our customers.  And, those people couldn’t do what they do without the courage and direction of our elite team of Product Owners and our senior leaders, who themselves have been on their own agile journey.  Thank you to the people of Valpak for your collective effort in another year of not just doing agile but being agile too.  Cheers to you!


Join Me at Agile2017

unnamed

 


Capitalization of IT Labor at Valpak

Been meaning to write this post for quite some time.  It’s not the most thrilling of agile topics so my procrastinator has been hard at work.

Let’s talk about the capitalization of IT labor!  Woo hoo!

Some of you may recall, if you’ve been following along, that Valpak was acquired by a private equity firm in January of this year.  With that came many changes including the direction from our new owners to capitalize on certain large IT projects (Valpak was previously owned by Cox Media Group which neither required nor encouraged such things).  Initially, this lead to a panic among us leaders.  How can we be agile while having to account for every minute of our time? 

After the initial panic subsided and we started doing some research, we found that there are very agile ways of handling IT labor capitalization.  In fact, we learned that there is no one right way to meet the GAAP standard.  There was hope for us after all!

Before I get down to the nitty-gritty business of capitalization, I’d like to share with you a few resources I found helpful along the way.

  • A super insightful blog post by Catherine Connor of 101 Ways on The Top 10 Pitfalls of Agile Capitalization
  • Very handy documentation from the Scaled Agile Framework (SAFe) folks on CapEx and OpEx with some great illustrations for understanding the concepts and options.
  • Last but not least, Pat Reed’s work on the Agile Accounting initiative as part of the Agile Alliance provides a great overview.  The Citrix case study is helpful too, but be be warned that if you contact the person that wrote it they will want to charge you $400/hour to answer your questions.

Now, let’s get down to it … I won’t bore you with the various permutations we attempted over the first few months (there was some pain involved).  Rather, I’ll jump to the good stuff … I have for you our IT Capitalization Policy as documented by myself and approved by our Accounting department and our auditors.

IT Capitalization Policy at Valpak

The following documents the policy for capitalizing software development costs at Valpak.  Not all projects will be capitalized.  Only certain large IT projects will be capitalized.  Projects to be capitalized will be identified each year as part of the budget process.

All software development work to be capitalized will be identified at the story level.  Stories to be capitalized will be flagged in Target Process as CapEx by the Agile Project Leader as part of the team’s process.  Budgeted projects will be capitalized using one of two methods, either by story count or actual hours.  Scrum teams will use the story count method.  Kanban teams will choose either story count or actual hours based on what is most accurate for their process.  The method applied will be consistent for any given team.  The Agile Project Leaders will maintain detailed calculations for all their teams and ensure auditability of data in Target Process.

For the story count method, stories are counted by the month in which they are completed (not necessarily released) in order to determine the percent of stories completed that are CapEx for any given team.  The CapEx percent is then applied to the number of available work hours in a given month to determine how many of those work hours are to be capitalized.  In addition, shared resources are taken into account and available work hours reduced by PTO.

In some special cases where a person on a team is solely focused on certain stories (not contributing to all of the stories in a given month), it may be more accurate to apply the story count method at the individual person level rather than the team level.   For instance, Team A completes 1 of 20 CapEx stories and that one story was the sole focus of a single person for 100% of their available work hours.  In such cases, the Agile Project Leader will determine the more accurate level at which to apply the story count method, team or person, and calculate accordingly.  Where person-level story count is applied, it will be notated in the detailed spreadsheets.

Here are several examples of the story count method applied:

  • A person dedicated to a single team who has worked every day in January (no PTO taken).  Their team completes 17 CapEx out of 20 stories in January or 85%.  There are 20 work days in January for a total of 160 hours.  This equates to 136 CapEx hours for this person.
  • A person dedicated to a single team who took a week off in January.  Their team completes 17 CapEx out of 20 stories in January or 85%.  There are 20 work days in January for a total of 160 hours but they took 40 of them as PTO for a subtotal of 120 hours.  This equates to 102 CapEx hours for this person.
  • A person split (shared) 50% between two teams in January.  Team A completes 17 CapEx out of 20 stories in January or 85%.  Team B completes 10 CapEx out of 15 stories in January or 67%.  There are 20 work days in January for a total of 160 hours.  This equates to 68 CapEx hours for this person for Team A (160 hrs x 50% x 85%) and 53.6 CapEx hours for this person for Team B (160 hrs x 50% x 67%).  If this split person took PTO, it would be taken out of the monthly available hours first.

The actual hours method may be applied by Kanban teams where it is determined to be the more accurate approach for their process.  Actual hours will be recorded by each team member for CapEx stories in Target Process.  The Agile Project Leaders will collect and report the actual CapEx hours for all team members each month.

For project leadership roles like Agile Project Leaders, a projected allocation will be applied each month to their available work hours.

 


My Mom, The ScrumMaster

Picture1A very special Mother’s Day edition of iamagile.

Have I told you the story of the woman that reinvented herself as a ScrumMaster in just 3 short months?  Well, that’s the story of my mom, Dottye Stewart.

As the story goes, this isn’t the first time my mom has reinvented herself.  She started out as a widowed mom to two daughters, pursuing higher education to be a positive role model for my sister and me.

After earning her MBA in Finance back in the 80’s, she did the consulting circuit for a while then quickly gained success in the life insurance industry as a marketing and business development executive.   After finding herself in a dead end job with a dead end, and morally corrupt, company last year (I won’t name names but I’m certain you could figure it out), she came to me and said, “I’m going become a Scrum Master”.  Admittedly, I laughed a little on the inside thinking there is no way someone can reinvent themselves into a Scrum Master at this point in their career.  Boy was I wrong!  If you ask my mom, she will tell you she’s been an agile leader throughout her entire work-life.  Not because she’s been subjected to my agile ways, but rather because of something called “facilitative leadership” that she learned while at GE Capital.

In October 2016, my mom began attending Tampa Bay Agile meetups regularly and, being the extreme extrovert in the family, she quickly became the social director for the ScrumMasters Guild, personally connecting with each and everyone.  Before 2016 was over, my mom had earned the Professional Scrum Master (PSP) and the ICAgile Certified Professional (ICP) and was being personally mentored by some of the best Agile Coaches in Tampa Bay from the AgileThought team.  By January 2017, my mom was gainfully employed at Bankers Financial as an Agile Coach and ScrumMaster.  That takes us to today.   While Bankers has been great training ground, she is openly pursuing new opportunities as ScrumMaster to continue along on her agile journey.

I guess the apple doesn’t fall far from the tree or, in this case, maybe the tree follows the apple.  I hope you are pleased to meet My Mom, The ScrumMaster.

Happy Mother’s Day Mom. You make me so proud to be your daughter!


How Do You Like Motherhood?

It’s been a while since I last posted … December, I think.  Some of you may recall, I was pregnant.  I gave birth to a healthy, handsome baby boy, Jetsen Edison Davis, on February 2nd and I’ve been so consumed with motherhood that I just haven’t had any interest or time for much else, including blogging.  Well, I’m back to work and I’ll be back to blogging soon enough.  I’ve got a few ideas percolating now.  Meanwhile, let me leave you with the answer to the question I’m asked most nowadays:  How do you like motherhood?

So far, I’m finding motherhood to be the most fulfilling thing I’ve ever experienced in my entire life.  To me, motherhood has been more fulfilling than any degree I’ve earned, award I’ve won, or relationship I’ve had … and yes, even more fulfilling than agile.  Until recently, I didn’t truly understand the love I would feel for this little being.  It’s truly magical!


About An Agile Pregnancy

7263decc-cbb9-4d74-94c2-e4a952ab958f-2

A few months ago my husband and I announced that we were expecting in February 2017.  Being the geeks we are, we announced “It’s a boy!” soon after with a line of binary code (that truly drove our families and not-so-geeky friends nuts trying to figure that one out).

It wasn’t long before I became overwhelmed by the sheer number of activities needed to prepare for Baby Davis’ arrival, involving nursery and supplies, classes and books, doctors and tests, and everything in between.  I’m convinced the gestation period for a baby is 9 months because the preparations take equally as long.

Being the proud agilist I am, I quickly turned to agile.  Yes, that’s right, agile can be applied to pregnancy too!  Here for your amusement and enlightenment is the first draft of my Baby Davis Trello board complete with a backlog organized by trimester.  Enjoy!

baby-davis-trello