- Blog Categories
- Project Management
- Agile Management
- IT Service Management
- Cloud Computing
- Business Management
- Business Intelligence
- Quality Engineer
- Cyber Security
- Career
- Big Data
- Programming
- Most Popular Blogs
- PMP Exam Schedule for 2024: Check PMP Exam Date
- Top 60+ PMP Exam Questions and Answers for 2024
- PMP Cheat Sheet and PMP Formulas To Use in 2024
- What is PMP Process? A Complete List of 49 Processes of PMP
- Top 15+ Project Management Case Studies with Examples 2024
- Top Picks by Authors
- Top 170 Project Management Research Topics
- What is Effective Communication: Definition
- How to Create a Project Plan in Excel in 2024?
- PMP Certification Exam Eligibility in 2024 [A Complete Checklist]
- PMP Certification Fees - All Aspects of PMP Certification Fee
- Most Popular Blogs
- CSM vs PSM: Which Certification to Choose in 2024?
- How Much Does Scrum Master Certification Cost in 2024?
- CSPO vs PSPO Certification: What to Choose in 2024?
- 8 Best Scrum Master Certifications to Pursue in 2024
- Safe Agilist Exam: A Complete Study Guide 2024
- Top Picks by Authors
- SAFe vs Agile: Difference Between Scaled Agile and Agile
- Top 21 Scrum Best Practices for Efficient Agile Workflow
- 30 User Story Examples and Templates to Use in 2024
- State of Agile: Things You Need to Know
- Top 24 Career Benefits of a Certifed Scrum Master
- Most Popular Blogs
- ITIL Certification Cost in 2024 [Exam Fee & Other Expenses]
- Top 17 Required Skills for System Administrator in 2024
- How Effective Is Itil Certification for a Job Switch?
- IT Service Management (ITSM) Role and Responsibilities
- Top 25 Service Based Companies in India in 2024
- Top Picks by Authors
- What is Escalation Matrix & How Does It Work? [Types, Process]
- ITIL Service Operation: Phases, Functions, Best Practices
- 10 Best Facility Management Software in 2024
- What is Service Request Management in ITIL? Example, Steps, Tips
- An Introduction To ITIL® Exam
- Most Popular Blogs
- A Complete AWS Cheat Sheet: Important Topics Covered
- Top AWS Solution Architect Projects in 2024
- 15 Best Azure Certifications 2024: Which one to Choose?
- Top 22 Cloud Computing Project Ideas in 2024 [Source Code]
- How to Become an Azure Data Engineer? 2024 Roadmap
- Top Picks by Authors
- Top 40 IoT Project Ideas and Topics in 2024 [Source Code]
- The Future of AWS: Top Trends & Predictions in 2024
- AWS Solutions Architect vs AWS Developer [Key Differences]
- Top 20 Azure Data Engineering Projects in 2024 [Source Code]
- 25 Best Cloud Computing Tools in 2024
- Most Popular Blogs
- Company Analysis Report: Examples, Templates, Components
- 400 Trending Business Management Research Topics
- Business Analysis Body of Knowledge (BABOK): Guide
- ECBA Certification: Is it Worth it?
- How to Become Business Analyst in 2024? Step-by-Step
- Top Picks by Authors
- Top 20 Business Analytics Project in 2024 [With Source Code]
- ECBA Certification Cost Across Countries
- Top 9 Free Business Requirements Document (BRD) Templates
- Business Analyst Job Description in 2024 [Key Responsibility]
- Business Analysis Framework: Elements, Process, Techniques
- Most Popular Blogs
- Best Career options after BA [2024]
- Top Career Options after BCom to Know in 2024
- Top 10 Power Bi Books of 2024 [Beginners to Experienced]
- Power BI Skills in Demand: How to Stand Out in the Job Market
- Top 15 Power BI Project Ideas
- Top Picks by Authors
- 10 Limitations of Power BI: You Must Know in 2024
- Top 45 Career Options After BBA in 2024 [With Salary]
- Top Power BI Dashboard Templates of 2024
- What is Power BI Used For - Practical Applications Of Power BI
- SSRS Vs Power BI - What are the Key Differences?
- Most Popular Blogs
- Data Collection Plan For Six Sigma: How to Create One?
- Quality Engineer Resume for 2024 [Examples + Tips]
- 20 Best Quality Management Certifications That Pay Well in 2024
- Six Sigma in Operations Management [A Brief Introduction]
- Top Picks by Authors
- Six Sigma Green Belt vs PMP: What's the Difference
- Quality Management: Definition, Importance, Components
- Adding Green Belt Certifications to Your Resume
- Six Sigma Green Belt in Healthcare: Concepts, Benefits and Examples
- Most Popular Blogs
- Latest CISSP Exam Dumps of 2024 [Free CISSP Dumps]
- CISSP vs Security+ Certifications: Which is Best in 2024?
- Best CISSP Study Guides for 2024 + CISSP Study Plan
- How to Become an Ethical Hacker in 2024?
- Top Picks by Authors
- CISSP vs Master's Degree: Which One to Choose in 2024?
- CISSP Endorsement Process: Requirements & Example
- OSCP vs CISSP | Top Cybersecurity Certifications
- How to Pass the CISSP Exam on Your 1st Attempt in 2024?
- Most Popular Blogs
- Best Career options after BA [2024]
- Top Picks by Authors
- Top Career Options & Courses After 12th Commerce in 2024
- Recommended Blogs
- 30 Best Answers for Your 'Reason for Job Change' in 2024
- Recommended Blogs
- Time Management Skills: How it Affects your Career
- Most Popular Blogs
- Top 28 Big Data Companies to Know in 2024
- Top Picks by Authors
- Top Big Data Tools You Need to Know in 2024
- Most Popular Blogs
- Web Development Using PHP And MySQL
- Top Picks by Authors
- Top 30 Software Engineering Projects in 2024 [Source Code]
- More
- Agile & PMP Practice Tests
- Agile Testing
- Agile Scrum Practice Exam
- CAPM Practice Test
- PRINCE2 Foundation Exam
- PMP Practice Exam
- Cloud Related Practice Test
- Azure Infrastructure Solutions
- AWS Solutions Architect
- AWS Developer Associate
- IT Related Pratice Test
- ITIL Practice Test
- Devops Practice Test
- TOGAF® Practice Test
- Other Practice Test
- Oracle Primavera P6 V8
- MS Project Practice Test
- Project Management & Agile
- Project Management Interview Questions
- Release Train Engineer Interview Questions
- Agile Coach Interview Questions
- Scrum Interview Questions
- IT Project Manager Interview Questions
- Cloud & Data
- Azure Databricks Interview Questions
- AWS architect Interview Questions
- Cloud Computing Interview Questions
- AWS Interview Questions
- Kubernetes Interview Questions
- Web Development
- CSS3 Free Course with Certificates
- Basics of Spring Core and MVC
- Javascript Free Course with Certificate
- React Free Course with Certificate
- Node JS Free Certification Course
- Data Science
- Python Machine Learning Course
- Python for Data Science Free Course
- NLP Free Course with Certificate
- Data Analysis Using SQL
The Importance of the Transparency Value in Agile
Updated on 28 September, 2017
9.45K+ views
• 16 min read
Table of Contents
Transparency is one of the core values of Agile. Transparency is critical to the success of organizations and groups adopting Agile. In Scrum, we use burndown and/or burnup charts to report the progress of the team throughout the Sprint. In Scrum, we also have “ceremonies” or meetings that help with transparency, which include the Daily Standup, Sprint Planning, Sprint Review, and Retrospective meetings. These all give the team and product owner a chance to raise issues and be honest about things like the team’s progress. We can also implement a 5 whys root cause analysis process in the agile team to identify the main problem solution. The meetings also give the team a chance to adapt and improve. Get to know more about agile vs traditional project management.
Why is transparency important to Agile?
Transparency in Agile Software Development cannot be overstated. In some organizations it is not easy to be transparent and open. There are lots of pressures to say what the business wants to hear. But I believe in the long-run a lack of transparency hurts an Agile team, the project, the organization, and ultimately the company.
I have seen firsthand organizations that claim they want “openness” but then, I can say that true transparency is not easy. Transparency is critical to the success of Software Development using Agile Methodology and it is well worth the effort.
Without full transparency there are lots of bad things that happen, including:
- Lack of trust with the Product Owner
- Team has to get caught-up in politics instead of focusing on what needs to be delivered
- Team morale can suffer
- Measuring future work is more difficult
- The team’s true velocity is not known
How teams can be more transparent with a Product Owner
There are several steps a team can take to prevent the issues raised in the previous section. In this section, we will cover some of those steps.
Use burndown charts to be honest about how the team is performing in a given Sprint. A burndown chart tells the true story of how the team is performing. Some teams also use a burnup chart for this purpose. If you cliff-dive at the end of the Sprint, that's not the greatest, but at least you are being honest to the Product Owner in terms of what happened.
If you are not going to make the Sprint commitment, at least that will be more obvious during the Sprint (i.e. the burndown will show that the team is not closing enough points each day and is at risk of either cliff-diving or not meeting the commitment). The point is that the team is being completely transparent. The velocity is what it is. The product owner knows what the team is capable of delivering.
Using the raw data and not hiding anything from the business frees an Agile team. I believe it is Kent Beck that has an excellent quote in one of his presentations about what he calls “schedule chicken.” He tells a story about people around the table during a typical project meeting and the project manager is going around asking each team how things are going. Everyone wants to put on a good face and says “umm, yeah we are on schedule” even when they are not. Now they have to sit there and know that they might be caught in a lie later.
Better to just be honest and say “Well, we are about 2 Sprints behind.” Done. Now there is nothing to hide and you can move on and deal with the reality of the situation you are faced with.
There are a couple things that happen when the team is honest with the Product Owner. The first, as mentioned previously, is the relationship between the Product Owner’s trust in a team and the team’s transparency. Figure 1 below shows this relationship.
But there is another benefit we get from being transparent: the team’s velocity becomes more accurate. This can be seen in Figure 2 below.
What Product Owners Should Ask
If you are a Product Owner what are some of the signs that a Scrum team is not being 100% transparent? This section will focus on some of the red flags or “smells” that may indicate a team is not being truthful and transparent.
If a team does not want to share their burndown and/or burnup charts, that is an obvious red flag and is simply not acceptable.
If the velocity of a team is very static, that may also indicate issues. This may indicate that the team has a fixed amount of points they will always commit to for a Sprint, regardless of their actual capacity. More on this in the section below on case studies.
Another possible red flag is when most User Stories have the same point value. It could indicate that the team is using a “one size fits all” for their estimates. The Product Owner should not be afraid to press the team if they feel the team is not accurately estimating User Stories. But you need to ask in a way that is not accusatory.
Become a project management expert with our PMP online training courses. Enhance your career and confidently lead successful projects.
Case studies
In one Scrum team I saw a real lack of transparency and it really was not a good experience. Soon after joining this Scrum team, I attended my first Sprint Planning meeting on this team. In the meeting I noticed something odd. Their true velocity was let's say, 40 points, but they would only commit to around 30 points. They would then find a few more stories and put them in the next Sprint. These additional stories were what they would call “a stretch goal”. But they knew their velocity was much higher than what they were committing to. This seemed very wrong to me. It was a total lack of transparency and honesty.
Not surprisingly, the team would typically finish the stories in the current Sprint and then work on a few more stories from the next Sprint that they had put aside. For the most part, this was a management decision because they did not trust the team to meet their velocity in a consistent fashion. This led to a lack of transparency with the business, and normal tools like burndown charts could not be trusted. Also, it did not make the team feel very good because they knew they were not being honest with the business.
Instead of using this "stretch goal" approach, use the velocity of the team to measure how much work can be done in a given Sprint. Then, based on capacity, commit to what you know your team can complete that Sprint.
Be honest about the team’s velocity and don't give into political games about trying “to look good” on some presentation slide. This type of misrepresentation does not benefit anyone in the long run.
Conclusion
The bottom line is to let the quality of the team’s work speak for itself. Have a consistent velocity, deliver software without defects, deliver business value, and adapt to what the business needs. This will lead to more trust with the Product Owner and will make the team feel better since they are being 100% honest not having to play any games. This lets the team focus on what truly matters: delivering quality software that adds value.