Blog

Our Thanks To Attendees of Global Day of Coderetreat 2014!!!

By: Agile Velocity | Nov 25, 2014 |  Article

Global Coderetreat 2014!Agile Velocity had a great time hosting and facilitating a location in Austin during Global Day of Coderetreat 2014! This was our first time hosting and facilitating this event and we enjoyed the group that came out for some community, learning, and deliberate practice!We had a small group (largely due to our late entry into hosting this year) but everyone was engaged and interactive.

Participants also enjoyed BBQ and interactive video chats with other participating groups around the world during breaks. We interacted with groups from Finland, Mexico, and other US locations highlighting the worldwide participation of developers.

Participants spent time pair programming, writing good tests, and focusing on simple design while implementing the game of life. We changed the way we approach solving problems by applying constraints such as limiting the lines of code per method, eliminating branching structures, and limiting ourselves to use of immutable objects. Each of these activities focused us on practicing doing things well and finding new ways to solve problems so that we are more effective in our daily team environments and under the pressure of delivery.

If you have never attended a Codetreat we recommend reading up and try one the next time you have an opportunity. We certainly hope to host one again!

Blog

Agile Benefits – Deliver Double the Value

By: Agile Velocity | Nov 05, 2014 |  Article,  Leadership,  Scrum,  ScrumMaster

Are you successfully realizing agile benefits and effectively delivering software?

David Hawks, CST, CSC, and CEO of Agile Velocity, demonstrates how our Technical Player-Coaches work with your team(s) and help organizations realize a 50% gain in productivity.

Say you need to get 50% productivity increase, if I have a team of 6 people, you can add 3 people, but there are a lot of logistical problems with that, and it takes a lot of time. Or you can go Agile.

One of the difficulties of Agile is that you don’t know what you don’t know. We started a project where we were gonna do four 2-week sprints, and at the end of the fourth sprint, we had planned a 2 week hardening sprint, where we fixed everything. We thought we were getting it done, but it wasn’t done-done. We pushed the bugs out, deferring them. So the bug fixing ended up taking 8 weeks. It ended up taking much longer because we weren’t getting things to completion. Going slow to go fast would have been faster. You can realize value earlier.

Want to deliver double the value in half the time?  Click here to learn more about Technical Player-Coaches and how they can help your organization.

More posts:

Using Agile to Deliver Double the Value in Half the Time Series

Blog

The Technical Debt Game

By: Agile Velocity | Oct 21, 2014 |  Article,  Technical Practices

Technical Debt

Every software project has it. Technical debt in a software project is essentially a backlog of technical stories the development team thinks need to be completed that are not visible to the product owner and don’t directly implement user features. These stories arise from either the inevitable trade-offs made during rapid implementation, or from inadvertent discoveries after implementation that some code should be refactored. By itself, technical debt is not a bad thing. It’s more prudent to “minimally” implement some features to get rapid feedback, and only later more fully flesh-out the implementation after requirements are more clear.

Impact of Technical Debt

Technical debt has a constant impact on the efficiency of the development team. Technical debt makes completing feature stories more difficult than it would otherwise be. Technical debt can make the code base more difficult to understand and can lead to a higher defect rate. Perhaps the most frustrating aspect of Technical Debt is that it is very difficult to quantify its impact. This makes it difficult for the development team to make the case with their Product Owner for reducing tech debt. The development team is usually left using financial (or even food) metaphors to help convey why tech debt stories should be tackled sooner rather than later.

The Tech Debt Game

Technical Debt Game-Agile Velocity

 

To help demonstrate and better understand the trade-offs and various strategies tech debt can have, my colleagues and I have developed a “Tech Debt Game” which can be used to simulate development iterations with both feature backlogs and technical debt backlogs. Players can try out different strategies of dealing with the tech debt with the goal of completing the most feature story-points. This game can be used as a way to demonstrate the impact of technical debt and help start the conversation with Product Owners and other external stakeholders.

Get the Tech Debt Game

Blog

Being Agile – Deliver Double the Value in Half the Time

By: Agile Velocity | Oct 01, 2014 |  Agile Transformation,  Article

David Hawks’ presentation, Being Agile vs. Doing Agile: Deliver Double the Value in Half the Time, given at the PMI conference in Austin, September 2014.

Being Agile:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development processes harness change for customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale.
  4. Business people and developers must work together daily throughout the project
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhanced agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architecture, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

For more on our approach to building lasting business agility, you can check out our Transformation Services page.

Blog

What are your biggest risks in Product Development?

By: Agile Velocity | |  Article

Play Product Madness - Risks in Product DevelopmentWe asked Product Managers, Business Analysts, and Project Managers to identify their most challenging product development risks.  See how these three professional groups ranked the risks.

Business Analysts:  Risks in Product Development

1. Product incompletely addresses the needs of targeted users
2. The design of the product is inherently flawed
3. The product is not differentiated from alternative solutions
4. Product launch is delayed, delaying revenue
5. The product did not solve enough problems, or solve them sufficiently

Product Managers:  Risks in Product Development

1. The buyer does not perceive that the product provides enough value
2. Product incompletely addresses the needs of targeted users
3. The design of the product is inherently flawed
4. Customers are unwilling or unable to pay for the product
5. The product did not solve enough problems, or solve them sufficiently

Project Managers:  Risks in Product Development

1. Our team does not know how to sell into this market
2. Product does not incorporate the context of usage into design / features
3. Product does not account for user’s learning curve or level of expertise
4. The product’s features are not aligned with the customer’s competitive strategy
5. Our market selection is not aligned with the rest of our strategy

Conclusion of the Results

Even though the top five product development risks differed between the experts, there was a common theme around user experience.

Business analysts and product managers agree that two of the top three risks include design flaws, design not fulfilling needs of customers and the customer’s problems were not solved through the product.  The Standish Report says that 64% of product features are rarely or never used. There’s a huge cost given the time that goes into shipping and maintaining those features. In addition to this cost, there’s the missed opportunity of delighting the customers with otherwise valuable features.

Project managers were drawn to risks involving how the user will interact with the product. Given an ever increasing competitive market, it is crucial companies take the time to analyze how the user will use the product. If products aren’t designed in a way that is intuitive to the customer, the competition may outperform.
Here are some recommended tools that have helped attune many companies to their customers.

  • Product Owner’s Guide: Keys to Product Planning
    This guide is a “cheat sheet” for product owners outlining steps to product planning success. Easy-to-use templates are included to create a product vision, definite customer personas, and more.
  • Story Mapping
    Story mapping helps the team understand the workflow, see the relationship of larger stories to “child” stories, know how to validate when a story is complete, and gives a context for prioritization.

What tools have you successfully used to be more in tune with customers?

Contact us about onsite coaching for help implementing any of these ideas.

Blog

Energize Your Meetings Series

By: Agile Velocity | Sep 16, 2014 |  Article,  Scrum,  ScrumMaster

energize your meetings with more than coffeeAll of us have led or attended meetings that were boring or a waste of time.  We aspire to lead meetings so people are engaged, actively contributing, and eager to help solve the pressing problems. In this blog series, we’ll share exercises increasing engagement and ways to energize your meetings.  These are great tips for Scrum Masters, team leaders, project managers, and facilitators.

Exercises to Break the Ice – Exercises such as Ball Toss Name Game and Progressive Story

Exercises to Encourage Brainstorming – Exercises such as Ball Toss Game and Pass the Card

Exercises to Prepare for Long Meetings – Exercises such as James Bond and Elephant

http://gamessimonplays.com/

Blog

Energize Your Meetings – Exercises to Prepare for Long Meetings

By: Agile Velocity | |  Article,  Scrum,  ScrumMaster

Exercise equipment to prepare for long meetingsThis is Part 3 of a 3-part blog series for Scrum Masters, Product and Product Managers, and facilitators.  Use these exercises to lead long meetings that are fun and energized, resulting in more participant engagement.

These exercises are great for re-energizing a group, especially in long meetings.  Highly interactive, these exercises are fun and also break down boundaries within a group.

Bibbity-Bobbity-Bop

Supplies and Room Requirements:

  • Enough space for people to form circles and move around

Setup:

Goal: get someone to take your place in the middle

  1. Stand in a circle with at least 9 people.
  2. Someone stands in the middle of the circle.
  3. Women may want to take off heels so they can do small jumps.
  4. Be prepared for highly interactive exercise!

 

Round 1 – Bibbity-Bobbity-Bop:

  1. Person in the middle approaches anyone in circle and says:
  • “Bibbity-Bobbity-Bop” or
  • “Bop”
  1. In order to avoid going to the middle you must:
  • Say “Bop” before they finish “Bibbity-Bobbity-Bop” or
  • Say nothing in response to “Bop”

 

Round 2 – James Bond:James Bond Game for long meetings

  1. Person in middle approaches anyone in circle says:
  • “James Bond 1,2,3,4,5,6,7,8,9,10”
  1. Before they reach 10, the person challenged must:
  • Adopt and hold the James Bond position
  • Person on each side become Bond girls who cry “Oh James, Oh James”
  1. Anyone not in position by the count of 10 must go in middle of circle.
  2. Can use methods from round 1

 

Elephant Game for long meetingsRound 3 – Elephant:

  1. Person in middle approaches anyone in circle says:
  • “Elephant 1,2,3,4,5,6,7,8,9,10”
  1. Before they reach 10, the person challenged must:
  • Adopt and hold an elephant position
  • Person on each side forms elephants ears
  1. Anyone not in position by count of 10 must go in middle
  2. Can use methods from other rounds

 

Round 4 – Toaster:

  1. Person in the middle approaches anyone in the circle says:
  • “Toaster 1,2,3,4,5,6,7,8,9,10”
  1. Before they reach 10, the person challenged must:
  • Jump up and down like a piece of toast popping out of a toaster
  • Person on each side forms the toaster
  1. Anyone not in position by count of 10 must go in middle
  2. Can use methods from other rounds

 

Resources:

http://gamessimonplays.com/

Exercises to Break the Ice

Exercises to Encourage Brainstorming

 

 

Blog

Energize Your Meetings-Exercises to Break the Ice

By: Agile Velocity | |  Article,  Scrum,  ScrumMaster

submarine in the arctic used to break the iceThis is Part 1 of a 3-part blog series for Scrum Masters, Product and Product Managers, and facilitators.  Use these exercises to break the ice and lead meetings that are fun and energized, resulting in more participant engagement.

Exercise 1: Ball Toss Name Game

This exercise is a great way to breath the ice for newly formed teams. It can also be used to introduce teams across the organization.

Supplies and Room Requirements:

  • Light, soft ball
  • Space for team to form a circle

Steps:

  1. Team forms a circle.
  2. Go around the circle and ask each team member to introduce himself or herself.
  3. One person takes ball and says another person’s name while tossing the ball to them.
  4. Keep going until the team knows the names of the people in the circle.

Exercise 2: Progressive Story

Progressive story is a good way to start a meeting, regardless of length or topic. This exercise inspires equal participation, as everyone is encouraged to provide input. It is also good for breaking down boundaries given that the exercise promotes uniformity.

Supplies and Room Requirements:

  • None

Steps:

  1. Explain steps and ask one person to start the story with a 1-2 sentence prompt.
  2. Go around room and each team member continues the story by adding 1-2 sentences.
  3. Keep going until everyone has participated.

References:

http://gamessimonplays.com/

Exercises to Encourage Brainstorming

Exercises to Prepare for Long Meetings

Learn more leadership tools in Advanced ScrumMaster Skills training.

Blog

Energize Your Meetings – Exercises to Encourage Brainstorming

By: Agile Velocity | |  Article,  Scrum,  ScrumMaster

Lightbulb in a thought bubble...brainstormingThis is Part 2 of a 3-part blog series for Scrum Masters, Product and Product Managers, and facilitators.  Use these exercises to incite brainstorming meetings that are fun and energized, resulting in more participant engagement.

Exercise 1: Pass the Card

This silent exercise is helpful for gathering input from all meeting attendees. It is great for building on ideas and is especially effective for teams struggling with equal participation.

Supplies and Room Requirements:

  • Index cards
  • Sharpies

Steps:

  1. Team forms a circle around a table.
  2. Facilitator prompts sharing of topic themes the group would like to gather ideas on.
  3. Each person writes down one idea related to a topic.
  4. Pass the card to the person on the right.
  5. They add new ideas.
  6. Pass card with original and new ideas to right.
  7. Repeat until original card returns.

The purpose is to gather as many ideas as possible around a theme.  Encourage participants to write new ideas on each card.

 

Exercise 2: Ball Toss with Topic

This is a fun way to solicit input on a topic. It is a good way to energize the team.

Supplies and Room Requirements:

  • Light, soft ball
  • Space for team to form a circle

Steps:

  1. Facilitator shares a prompt question that the group would like to gather input on. If possible, post the question somewhere visible to the team.
  2. Team forms a circle.
  3. Toss ball to a team member.
  4. Receiving team member answers the question with an idea (or can pass).
  5. Facilitator captures answers somewhere visible to team.
  6. Keep going until team runs out of ideas.
  7. Review and discuss ideas.

Resources:

http://gamessimonplays.com/

Tabaka, J. (2006). Collaboration Explained. Addison-Wesley Professional

Exercises to Break the Ice

Exercises to Prepare for Long Meetings

Blog

Austin Business Journal-Best Places to Work

By: Agile Velocity | Jul 02, 2014 |  Agile,  Article

Austin Business Journal - Best Places to Work - The Agile Velocity Team

2014 Best Places to Work

The Austin Business Journal named Agile Velocity in the top ten of the best places to work in Austin for the micro companies category.  Agile Velocity was named to the list for the first time, ranking #8 out of 20 micro companies.  This award was announced at a luncheon hosted by the Austin Business Journal in Austin on June 26.

This is the first year Agile Velocity has been eligible for the Austin Business Journal award. Since its inception in 2011, Agile Velocity has grown from a single employee to over eleven with revenues increasing steadily each year.  Agile Velocity began when founder, David Hawks noticed companies ineffectively building innovative software products with a lot of waste.  With a background of building highly productive teams, David used these principles when establishing Agile Velocity.  Austin Business Journal recognizes these elements as key to creating companies that are fun and desirable places to work.

Companies are evaluated on areas that include:  benefits, job satisfaction, trust in leadership, the effectiveness of management, goal alignment, retention, and teamwork.  Kevin Tougas, the Staffing Solutions Manager at Agile Velocity says, “Collaboration, innovation, and team empowerment are the foundations to what we teach and what we live by at Agile Velocity.” Kim Phipps, the Marketing Manager at the company, said, “It is great to see Agile Velocity recognized locally.  It is a company that truly practices what it teaches and is an amazingly fun place to work.”

Agile Velocity is proud to represent micro-companies as an inspiring place to work.  It looks forward to continued growth and sharing of these principles with customers and the Austin community.