We have 3094 guests and 3 members online

Agile Blogs

Opinions by and for the agile community. Do you have an agile opinion? Add it Here
Tags >> julie
Aug 10

Scrum 1:2:2 (Month One:Week Two:Day Two)

Christen McLemore Posted by: Christen McLemore in Subscriptions | Comment (0)
Tagged in: scrum , rollout , project management , new job , julie , julia , agile

This is my second day of the second week of my first month at my new job.  The differences between me and the other Scrum Master are really style at this point so it doesn't make sense for me to sit in on all of their meetings anymore.  I've been focusing on the Business and the process they go through today to get work done.  Boy, it's a mess!  There are, by title alone, about 3 Project Managers for just about every area of the business and they don't seem to talk to each other much.  The PM at the outer most realm of the actual delivery team doesn't really know when or who works on their request and they appear to communicate solely via email with questions like "What's the status of x?" and "Is anyone working on Y?"  The most important thing for our teams right now is to find out WHO is doing WHAT and WHEN are they going to be done.  There is work being done already but it's unclear who has been assigned or what their schedules are.

 

Using my connections through LinkedIn, I was able to find out more than the Product Owner candidates resumes told me.  Our interviews for the new Product Owner are coming along but they won't start by the time we kick off our first sprint.  In the meantime, I've created a draft backlog with Business Owners, Resource names, Roles and requested launch dates so we can begin collecting every project known to the team.  We'll need to discuss what work must continue, what work should be transitioned.  As busy as it seems and chaotic as it is, this is when I get excited because bringing clarity to chaos is my specialty.  Bring it on!

Read More...
Aug 03

Scrum 1:1:2 (Month One Week One Day Two)

Christen McLemore Posted by: Christen McLemore in MyBlog | Comment (0)
Tagged in: scrum , rollout , project management , new job , julie , julia , agile

Today I spent my time in meetings.  I should just end right there because we all know that when you do that, you're not getting any actual work done.  It's the type of day that ends with you wondering where all your time went and how fifty people even know you're email address!  I managed to squeeze in a few minutes to sort through them and start organizing and prioritizing them so I can stay focused on the more important tasks for the week.  

 

If there's one thing I could share with anyone with time management challenges, it's to set up Outlook rules to presort incoming emails.  I've been doing this for so long I don't even know when I started it.  I've got some rules that automatically move meeting responses to the deleted folder, rules that move emails with certain subject words to a sub-folder, rules that send a notification to my cellphone when the CIO emails me, and others that do some fancier stuff when I need them (can't give away all my tricks just yet).  It has saved me hours of time not only checking my mail but also searching for mail.  I managed to crash a smoke break on the patio to discuss a candidate for the Product Owner on one of my teams, observe other team's Standup meetings, Demo prep discussions, Cross Team communication and sharing discussions, Sprint Demos, Retrospectives, and then I learned a little more about the company and the organization.  

Read More...
Aug 02

1:1:1 (Month One Week One Day One)

Christen McLemore Posted by: Christen McLemore in MyBlog | Comment (0)
Tagged in: scrum , rollout , project management , new job , julie , julia , agile

So it's the first day on the new team.  There are already two teams sprinting under a Scrum Master.  I've worked with him before indirectly and he's got the right experience and talent so it's going to be a great partnership once my two teams are in flight.  He's not a push over, not shy, and he's seasoned enough to know when he's hearing a bad idea but also open to hearing them before he says it's a bad idea.  We're going through the resource plans for the other two scrum teams that I'll be taking on.  I'm already planning for a Scrum training session for each of them but I'm going to play it by ear before i decide if both teams will be in the same session together.  We have a few openings on each team that we need to settle first; some hires, some transfers between teams.

The first two teams have already taken on names for their teams.  Their stand ups seem to be mature for a new team.  The team is on their feet for at least 15 minutes.  Everyone reports in the standard format; What did I accomplish since yesterday? What will I accomplish today? Do I have any roadblocks or impediments in my way?  They even report if the Scrum tools are accurate for our burndown charts.  They spend another 15 minutes or so (officially NOT part of the stand up) going through each story in a bit more detail to catch up on any detailed discussion that wasn't covered in the stand up.  They currently use Rally for their backlog but I'm not sure if that's consistent across the department yet.  I'll be looking into their backlog and tracking tools more this week.

My Product Owner is actually leaving the company in a few weeks so there will be some transition necessary if I dont' get someone by the end of the week.  I also met two of the Delivery Leads (new role for me as well as the company) and the Dev Manager to discuss our working relationships and our goals.  We're still getting to know each other but since we all came from the same company before this one we already have some "war stories" to reminisce over.  My meeting with the PM that I will be replacing was much faster than I would have hoped but I'm sure it won't make much difference in the end.  Since the teams aren't formed yet, the work is being done by random resources with SME experience based on their Non-Discretionary status until we have fully functional scrum teams to begin working on a backlog.  This leads me to believe that as soon as we complete our first sprint, we'll already be outperforming what was done before!  I'm going to spend some time in the morning detailing a plan and begin scheduling the meetings for each milestone. Just a brainstorm in my next steps... I'll need to gather as much knowledge as I can about the architecture of the systems and the business to see the big picture more clearly.  Even if I don't have a new Product Owner in place, I'll start pulling together a draft of the backlog and begin grooming the Business Leads that the Product Owner will interface with so I can brief them on how the scrum looks and feels.  I may even do a quick Scrum session just for them.   I'll be traveling to another site this week to confirm the team members and the openings. I'll be traveling with my Scrum Master partner, Delivery Lead, and Dev Manager so if there is any room for process improvement or efficiency opportunities we'll probably spend the train ride discussing those.  So I've just built my own two week sprint!

Jul 28

Julie & Julia meet Scrum

Christen McLemore Posted by: Christen McLemore in MyBlog | Comment (0)
Tagged in: scrum , rollout , project management , new job , julie , julia , agile

I sit at my desk for almost the last time today.  I've been in this seat for about ten years. During those ten years,  there were times it was so uncomfortable that I'd rather be tearing out my toenails one at a time than do it another day and sometimes I woke up early just to get back in this seat.  I guess that's how work goes; when you have a bad one you suffer and moan and maybe get up the courage to get a new one and when you find a great one, you don't want to leave, you don't want to move and you certainly don't want to make too much noise about how much you love it or someone might take it away or give you too much of it and then you're back to moaning about it again.   But I love my job, right now, I still  love my job! And I'm leaving it.

I love my job so much I want more of it so I'm taking a chance, a risk, a leap to go somewhere that wants me for what I've already done and what I can do for them.  Pretty friggin' cool, right?!  Well, I'm nervous.  I've been blessed with a great team and a great manager (yeah, really, it does exist!) that even when they doubted me, they trusted me to push them to the next level and give Scrum a shot. So I'm nervous because I know that I've been living the dream and I'm voluntarily choosing to leave it and see if it can replicate itself for me somewhere else.  Am I smokin' the good stuff or what?

So this is going to be my Julie & Julia meet Scrum blog about how it goes.  My plan is to commit to at least six months of blogging about what happens, removing real names to protect the guilty and maybe even exaggerating a little bit for effect because, let's face it - that makes a better story!

Read More...

Agile Marketplace - Announcements and Special Offers

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper