Agile Team Coaches: What Do They Even Do?

| By agilevelocity in Uncategorized | 0 Comments

Agile coaches are subject matter experts in Agile principles and practices and they apply their knowledge towards guiding struggling individuals, teams, and organizations. They are called when teams and organizations begin their Agile transformation, or if they when teams start and see realize that the road to high-performance may be rockier than expected. In both settings, the mission for the Agile coach is clear: help make the people, teams, and organizations they’re working with better by unlocking their potential.  

Hmmmm….a little nebulous?

What “better” means is different for every organization. Organizations embark upon an Agile adoption because of concrete goals they hope to achieve: faster time to market, improved quality, or happier customers. At the beginning of each engagement, the coach will work with stakeholder to define success and how it will be measured.  

Read More »

Do You Know Your Company Objective?

| By wpengine in Process | 0 Comments

road-569013

 

In 2014, Rick Klau gave a seminar on OKRs at Google. He explained how the multi-billion dollar company started using this methodology as their internal grading system since they were a 40 man team. What is more astonishing is that more than a decade later, Google still uses OKRs across the entire organization. Suddenly everyone wanted to jump on the OKRs or Objectives and Key Results bandwagon. Quite a few Silicon Valley companies already use OKRs extensively to manage their goals.

So what sets OKR’s apart from other goal-setting frameworks?

Read More »

Technical Skills And The Product Owner

| By Resalin Rago in Product Owner, Scrum | 0 Comments

hiring

 

Product Owners are in high demand. Searching on Indeed for “Product Owner” pulled up 103 new jobs posted this month. While, its existence is relatively new compared to a Product Manager, it’s gaining attention as Agile and Scrum begin to overtake traditional methods of building software and managing creating projects.

The Product Owner (PO) is responsible for creating the product vision and guiding the team as they work to make the vision a reality. They are the bridge between stakeholders, team, and the end users. It’s a job that requires a number of different hard and soft skills, from knowledge of Agile and Scrum to a Mama bear instinct to protect the product.

One of the most frequently asked questions in our CSPO classes is whether technical knowledge is required in a Product Owner role. The short answer is no, but the long answer is that technical skills are helpful, but not in the way you might think.

When you’re looking for a new PO, you want someone steeped in product development experience (clearly). The list below consists of hard and soft skills required in the PO role in addition to the years of experience needed. Because this post pertains to product ownership, we prioritized it in order of least to most important. You’re welcome.

Read More »

Lessons Learned from an Ice Cream Social (A Retro On A Sprint Retrospective)

| By William Baxter in Agile, Scrum, ScrumMaster | 0 Comments

iceCream

 

Sprint Retrospectives…the other bookend to Sprints. Retros mark the official end of the Sprint and serves to provide teams the opportunity to reflect so that the next Sprint is even more efficient.
Like all meetings, Sprint Retrospectives can be very useful or attendants can leave feeling confused and even angry if they feel like their time was wasted. They require planning from the ScrumMaster for teams to reap its full benefits. There are a lot of Retrospective activities out there; it helps to know what kind the team needs.

Read More »

21 Flavors Of ScrumMaster Role Combinations – Pros and Cons

| By David Hawks in Scrum, ScrumMaster | 1 Comment

designer-must-wear-many-hats

In the perfect Agile world, a ScrumMaster is a ScrumMaster…and that’s it. There’s not a never-ending custody battle where a person goes back and forth between two roles. Unfortunately, we live in the real world. Often, people come to our CSM workshops with a divided workload and wearing different hats: Product Owner and Manager or Software Lead And ScrumMaster.

This post will discuss the pros and cons of various ScrumMaster combinations, beginning with the ideal combination, ScrumMaster – ScrumMaster (dedicated ScrumMaster).

Read More »

Sustainable Pace For Everyone (Including Agilists)

| By Reese Schmit in Agile | 0 Comments

sustainable-pace-for-everyone

 

Nod your head if you have said the following:

  • “I need a day off so I can get some work done.”
  • “I’ve been in meetings for the last 6 hours solid.”
  • “It feels like I haven’t been at my desk in two days.”
  • “I’ll get to that this weekend.”

You’ve likely heard phrases like this around the office or said them yourself too many times. According to a Families and Work Institute study one in three American employees are chronically overworked. Multitasking, interruptions, too many meetings and an overwhelming workload are sited as some of the main contributors to their inability to maintain a reasonable work week.  As Agilists we drive home the concepts of focus, prioritization and sustainable pace for our teams but the rest of the company is left out to dry, including ourselves.

Read More »

Scrum Events Are Necessary (And Not Evil)

| By David Hawks in Agile, Scrum, ScrumMaster | 0 Comments

american-football-referees-1476038_1280

Refs gather for a quick meeting

 

In Scrum, there exists a general confusion about the Scrum events, or meetings: when they happen, who attends and why they exist.

The last question comes up…a lot. There will be resistance to “all the overhead” of Scrum, meetings included. In order to convince others to participate in Scrum events you can’t just say, “those are the rules of Scrum.” Developers and managers need to be convinced, which means we Agilists need to make sure they understand the value. Here are the Scrum Events and a quick explanation of why they exist.

Read More »

Do this, Not that: 8 Bad Habits Sabotaging Your Agile Transformation

| By agilevelocity in Agile, Agile Transformation | 0 Comments

break bad habits, build good habits - motivational reminder on colorful sticky notes - self-development concept

There are a lot of bad work habits: being late, checking Facebook too* many times, not putting your dirty coffee mug in the dishwasher, and interrupting your coworkers during meetings. Bad habits are “bad” because results are negative. They become even more destructive when they directly oppose a goal, e.g., late-night eating when you’re trying to lose weight.

It’s the same with Agile.

During an Agile transformation or adoption, behaviors that were innocent, even positive, can pause momentum or even BLOCK progress. That’s because Agile is not just a process change. Truly becoming Agile involves updating practices and taking a long, hard look at company culture. Below are nine bad behaviors to curb and good replacements if you want to make sure Agile sticks.

Read More »

« Older posts