I personally feel like the above statement is applicable to many aspects of life and business.  However, for the purposes of this particular post, I want to focus on visibility as it relates to the Agile/Scrum process for software development.

Don’t hide your successes and failures; make them visible, learn, and evolve.

Visibility, even in this defined context, covers a wide surface area.  On one hand it refers to the ability to look internally at the release schedules, iteration plans and daily execution of tasks required to facilitate software development.  On the other hand it represents the ability for clients to stay tuned in to Beeline’s development roadmap and through Beeline’s Annual Customer Conference, focus groups and other product management touch points actually influence the features and functionality of Beeline’s Intelligent workforce solutions.

Visibility, on a continuous basis, enables the organization to make key adjustments based on client & market feedback, technology changes and more.  Through collaboration, with both internal and external team members and stakeholders, Beeline is able to deliver better software solutions that more accurately meet customer needs and ensure internal and external expectations and managed closely.

Agile/Scrum facilitates numerous opportunities to inspect the process and make adjustments to improve efficiency and productivity. Process inspection occurs daily beginning with the “daily scrum” (or standup) and continues through to the sprint review and retrospective. Each day, team members and other stakeholders will inspect project indicators, such as burndown charts, cumulative flow diagrams, and other metrics. This visibility will help to expose process issues as they occur and allow for swift adjustment.

Visibility facilitates agility.  Perhaps more importantly it helps to promote continuous improvement.  By openly sharing successes and failures the teams, and thus the organization, can steadily evolve how they work which will help to promote individual growth and the creation of better technical solutions.

Share on FacebookTweet about this on TwitterShare on VKShare on LinkedInShare on Google+Email this to someone