Overview of TFS Reports, comparing what is available between different Process Templates. This is a WIP, and will be updated soon with additional info on customizing reports.
Being Agile with Any Process Template in TFS 2012Angela Dugan
Using an Agile template does not MAKE you Agile. Using a CMMI template does not PREVENT you from being agile. In this talk, I compare and contrast the TFS process templates available out of the box, and relate the process template artifacts and features to the types of methodologies and practices they support.
This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.
Being Agile with Any Process Template in TFS 2012Angela Dugan
Using an Agile template does not MAKE you Agile. Using a CMMI template does not PREVENT you from being agile. In this talk, I compare and contrast the TFS process templates available out of the box, and relate the process template artifacts and features to the types of methodologies and practices they support.
This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.
It's not Scrum VS. Kanban! It is Scrum AND Kanban!Mahesh Singh
Kanban does not compete with Scrum. Kanban can be applied by Scrum teams to improve and address issues they might be facing with their development processes. Far too often, Kanban gets positioned as a replacement for Scrum, when it can really be a powerful tool for Scrum teams to improve their overall delivery capability!
Manage a Complex Test Effort with Lean and KanbanTechWell
“How absurd! She swallowed a bird. She swallowed the bird to catch the spider. She swallowed the spider to catch the fly. I don't know why she swallowed the fly. Perhaps she'll die.” The silly nursery rhyme teaches a serious lesson. Because software products are complex, we seek to manage them by spinning a complex web of processes and tools. Thankfully, not all complex problems demand complex solutions. Join Mike Duskis as he demonstrates how his test team employed kanban practices to manage the test work of a multi-national, multi-project department with a system of index cards on the wall. With the kanban system in place and lean practices driving decisions, the team simplified the prioritization process, improved test visibility, which led to better testing choices. Lean-kanban produced strong results at Mike's shop and could do the same for yours. Join Mike to learn how you can clarify and communicate your test effort—without swallowing any spiders.
More Information
Not sure which software development methodology is better, SCRUM or KANBAN? Our short webinar explains the similarities and differences between the two methods, as well as some advantages of both.
Kanban with scrum or is it scrum with kanban.001Tom Reynolds
Kanban and Scrum are both methods that when used correctly lead to more agile organisations and teams.
Are these methods mutually exclusive or can they be used in conjunction with one another?
In this session we will explore whether these methods can indeed be used together and if so how that might be possible. Can Scrum and Kanban exist together, work together, and together deliver higher agility and higher levels of benefits and value to the organisations that use them. Is it Kanban with Scrum or is it Scrum with Kanban, let’s explore together through this interactive session and find out for ourselves.
Brief overview of Scrum
Overview of Kanban principles and practices
Comparison of Scrum and Kanban
Overview of Scrum with Kanban
Basic Metrics of Flow
Visualizing Metrics of Flow
Experience Report
This presentation wants to share our experience on forming an integrated Development/QA team in Perficient projects applying Scrum, and some of our best practices on securing high quality.
Short introduction to Scrum - a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Team Foundation Server - Tracking & ReportingSteve Lange
Comprehensive presentation detailing reporting and tracking capabilities of Team Foundation Server. Focuses on Excel workbooks and Reporting Services, but touches on other technologies as well.
The primary metric in an Agile project is whether working software actually exists, and is demonstrably suitable for its intended purpose. This is determined empirically, by demonstration, at the end of every single iteration and product increment
All teams and projects are encouraged to pivot most of their measuring-attention to this fact. All other metrics are subordinate to that objective and the overriding goal of keeping the focus on rapid delivery of quality, working software.
It's not Scrum VS. Kanban! It is Scrum AND Kanban!Mahesh Singh
Kanban does not compete with Scrum. Kanban can be applied by Scrum teams to improve and address issues they might be facing with their development processes. Far too often, Kanban gets positioned as a replacement for Scrum, when it can really be a powerful tool for Scrum teams to improve their overall delivery capability!
Manage a Complex Test Effort with Lean and KanbanTechWell
“How absurd! She swallowed a bird. She swallowed the bird to catch the spider. She swallowed the spider to catch the fly. I don't know why she swallowed the fly. Perhaps she'll die.” The silly nursery rhyme teaches a serious lesson. Because software products are complex, we seek to manage them by spinning a complex web of processes and tools. Thankfully, not all complex problems demand complex solutions. Join Mike Duskis as he demonstrates how his test team employed kanban practices to manage the test work of a multi-national, multi-project department with a system of index cards on the wall. With the kanban system in place and lean practices driving decisions, the team simplified the prioritization process, improved test visibility, which led to better testing choices. Lean-kanban produced strong results at Mike's shop and could do the same for yours. Join Mike to learn how you can clarify and communicate your test effort—without swallowing any spiders.
More Information
Not sure which software development methodology is better, SCRUM or KANBAN? Our short webinar explains the similarities and differences between the two methods, as well as some advantages of both.
Kanban with scrum or is it scrum with kanban.001Tom Reynolds
Kanban and Scrum are both methods that when used correctly lead to more agile organisations and teams.
Are these methods mutually exclusive or can they be used in conjunction with one another?
In this session we will explore whether these methods can indeed be used together and if so how that might be possible. Can Scrum and Kanban exist together, work together, and together deliver higher agility and higher levels of benefits and value to the organisations that use them. Is it Kanban with Scrum or is it Scrum with Kanban, let’s explore together through this interactive session and find out for ourselves.
Brief overview of Scrum
Overview of Kanban principles and practices
Comparison of Scrum and Kanban
Overview of Scrum with Kanban
Basic Metrics of Flow
Visualizing Metrics of Flow
Experience Report
This presentation wants to share our experience on forming an integrated Development/QA team in Perficient projects applying Scrum, and some of our best practices on securing high quality.
Short introduction to Scrum - a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Team Foundation Server - Tracking & ReportingSteve Lange
Comprehensive presentation detailing reporting and tracking capabilities of Team Foundation Server. Focuses on Excel workbooks and Reporting Services, but touches on other technologies as well.
The primary metric in an Agile project is whether working software actually exists, and is demonstrably suitable for its intended purpose. This is determined empirically, by demonstration, at the end of every single iteration and product increment
All teams and projects are encouraged to pivot most of their measuring-attention to this fact. All other metrics are subordinate to that objective and the overriding goal of keeping the focus on rapid delivery of quality, working software.
This presentation highlights my Scrum Master experience. Quite often, companies and teams seeking Scrum Master support misinterpret being an Agile Coach as someone that is unfamiliar with performing the hands-on duties of a Scrum Master.
Whether I am supporting a single team in the role of Scrum Master, or assisting an entire Enterprise, the desired outcome remains the same--help teams achieve higher levels of performance through Agile/Lean thinking, processes, and practices.
This presentation details the essentials of Agile project progress report. This is a primer for Scrum Masters and Product Owners for providing the given essential details in their progress reports.
Moving 65,000 Microsofties to DevOps with Visual Studio Team ServicesVSTS Community MSFT
How do you migrate over 65,000 of the most demanding software engineers from infrastructure built up over decades of high-intensity work into a common engineering system based on modern software development technologies and best practices?
Feedback helps us to build stronger teams, supports more effective problem-solving and collaboration, and ultimately contributes to happier people delivering better products. Without effective feedback, we can spend time focusing on the wrong things, solving the wrong problems, maybe not even knowing about problems in the first place! In my experience, people are generally not confident in their feedback skills. This makes feedback feel risky, vulnerable, scary, even downright anxiety-inducing and so then they give no feedback at all.
Feedback Doesn't Have to Suck. In this fast-paced 20 minute session focused on supercharging your feedback skills, I will help you get a good foothold on where to start. We’ll warm up with an overview of what feedback is, attributes of high-quality feedback, and some “tips and tricks” to getting comfortable with giving and receiving candid feedback that has worked really well for me both as a manager and a team member. You’ll be a feedback champion before you know it!
VS Liv MSHQ 2022 - Measuring Up! How To Choose Agile Metrics - Dugan.pdfAngela Dugan
How many times have you been asked to deliver on metrics that did not make sense to you, that felt counterproductive to your or the team's effectiveness, or that were seemingly impossible to collect in a sane fashion? Oftentimes, I find that metrics being collected are ones that are easy to collect and report on but are not necessarily the ones that will help the team learn and improve.
When it comes to software delivery, lean and agile practices and methodologies have taken the lead. Metrics have lagged a bit and often rely on very waterfall-style milestones and phase-gates to determine a team's effectiveness. In the spirit of continuous improvement, this session will take a look at the measures we can and should collect from agile teams, why these metrics are relevant and interesting, and how we can use them to help our teams continuously improve.
VS Live 2021 Orlando - vst14 feedback skillsAngela Dugan
Feedback helps us to build stronger teams, supports more effective problem-solve and collaboration, and ultimately contributes to delivering better products. Without it, we can spend time focusing on the wrong things, solving the wrong problems, maybe not even knowing about problems in the first place!
So if feedback is critical to us growing and thriving, why aren't we all excitedly showering each other with feedback all the time, and BEGGING others to give it to us? In my experience, people are generally not enthusiastic or confident in their ability to give feedback. Feedback usually isn't happening because feedback feels risky, vulnerable, scary, even downright anxiety-inducing.
As a manager, leader, and coach of many teams over the last 20+ years, I can help you get a good foothold on where to start. Even better, I can tell you where the bodies are buried so you avoid some of the mistakes I've experienced over the years too.
In this session, we'll warm up with an overview of what feedback is and is not. We'll also review the qualities of high-quality feedback, as well as the other kinds of feedback so you know the difference. We'll finish off with a quick summary of some "tips and tricks" to getting comfortable with giving and receiving candid feedback that has worked really well for me. You'll be a feedback champion before you know it!
VS Live 2021 VST09 agile team metrics Fast Focus - angela duganAngela Dugan
Are you still relying on the old standbys like percent complete, velocity, and burndown for monitoring the progress of your teams or projects? Those metrics may not be telling you what you think they are! In this fast-paced discussion, we'll talk about some of the pitfalls of commonly used metrics, and make the case for not so commonly used measures that give you the insights that you're really striving for.
You will learn:
Understand the connection between what you measure, your team performance, and product quality
Explanation of how many commonly used metrics will fail to tell you what you really need to know
Familiarity with uncommonly used metrics that will more reliably tell you how well your project or team are really doing
THAT Conference 2021 - Level up your Feedback GameAngela Dugan
Feedback makes the world go around, and let’s be honest, many of us feel pretty unskilled at feedback - both at giving and receiving. As technologists, we thrive on experimenting, learning, and adjusting, which we cannot do without the input and perspectives of others around us.
So if feedback is critical to us growing and thriving, if feedback is truly a “gift”, what’s the deal? Why isn’t everyone wholeheartedly and excitedly showering each other with feedback all the time? In my experience, feedback isn’t happening because feedback feels risky, vulnerable, scary, even downright anxiety-inducing. Feedback is also something we’re not trained to do well if at all. Bad practices like the “feedback sh*t sandwich” is still common practice. It may even feel like a personal and professional bear trap! In this session, we’ll warm up with an overview of what feedback is and is not. We’ll also review the qualities of high-quality feedback, as well as the other kinds of feedback so you know the difference.
That conference tap, tap, tap communicationAngela Dugan
In the 20 or so years since I joined the tech community, I moved from an attitude of "please leave me alone in my cube to code and whatever you do don't talk to me!" to well, giving talks on the importance of communication in the software world. The tools and techniques I've come to know and love have changed over time, but a few things have remained constant.
1) Communicating openly and honestly at all times is HARD
2) Speaking from a place of vulnerability is RIDICULOUSLY HARD
3) Without 1 and 2 you're going to really struggle to be an effective and happy member of ANY software team
OK, there's a 4th thing.
4) The days of working alone in your cube like a hermit are largely over for software folks. It really doesn't have to suck. I swear it doesn’t.
During my brief time with you, I’m going to rumble with some touch topics and share some of my own embarrassing and enlightening stumbles. It will include things like delivering “bad news” to your client/manager/team and feeling good about it, managing conflict with others in healthy and productive ways, and delivering feedback without feeling like you (or the receiver) will vomit. These things are all very possible, and not that hard to master once you have some key tools and insights in your tool belt.
Agile days chicago 2018 - how do you measure up?Angela Dugan
How many times have you been asked to deliver on metrics that did not make sense, that were counterproductive to the team’s effectiveness, or the organization’s effectiveness? Did those metrics seem impossible to collect? Often times, the metrics being collected are the ones that are easy, and focused on individual “productivity”. How do we collect data that drives continuous improvement and promotes an open and trust-filled environment. How does that change at scale?
When it comes to software delivery, lean and agile practices have clearly taken the lead. This session will take a look at the measures we can and should collect across teams and organizations. We’ll dig into metrics that are relevant, interesting, AND useful, and discuss some of the common traps.
VS Live Chicago 2018 - how do you measure upAngela Dugan
How many times have you been asked to deliver on metrics that did not make sense, that were counterproductive to the team's effectiveness, or that were seemingly impossible to collect? Often times, the metrics being collected are the ones that are easy, but not necessarily the ones that matter.
When it comes to software delivery, lean and agile practices and methodologies have clearly taken the lead. In the spirit of Kaizen, this session will take a look at the measures you can and should collect from agile teams, why these metrics are relevant and interesting, and how you can use them to help your teams continuously improve.
Chicago Code Camp 2018 - Building strong teamsAngela Dugan
Building the “perfect team” seems like an impossible task these days. Can a truly “cross-functional” team even be built? How do you get introverts and extroverts (yes, they DO exist in IT) to play nice? Seems like these days you practically need a degree in psychology to get this right. But you don’t.
Over the course of my career, I’ve worked with my clients and my company to develop high functioning teams. I’ve found that regardless of focus (software development, marketing, sales), there are patterns to what makes teams successful, and what can hold them back from greatness.
In this talk, I’ll cover a couple of tools for understanding the needs and strengths of your individual team members, identifying strength gaps, and action items for creating a happy and well-balanced team that can get it done!
Dev up 2017 - Half Day Workshop: Getting your agile team unstuckAngela Dugan
Whether you've been working on an agile team for 6 months, or 6 years, the same obstacles tend to arise to trip us up over and over. Maybe your retrospectives feel more like a death march and no one is participating any more, or your daily stand-ups have bloated into 25 team member status meetings, or you have a QA team that feels buried by your fast-paced development team. These situations are unfortunately very common, and they lower team morale, lead to abandoned transformation initiatives, and ultimately your product and customers suffer because of it. But there's a better way! As an agile coach and consultant, I help software organizations stop the bleeding, mature their process, and develop into high functioning agile teams. And to be clear, I've made mistakes as well! I'd like to share with the audience my own experiences, including strategies that succeeded and failed in hopes of leading them down the path to getting their own teams "unstuck". I'll also give attendees an opportunity to share their own challenges, so that we can leverage those strategies to give them ideas for blasting through their own roadblocks.
Learning points:
Recognizing when your process, product, or people have gone off the rails by identifying "smells"
Review some tools and strategies that teams can leverage when they need a cognitive reset to get them back on track
How to apply tools and strategies in your own unique environments.
How many times have you been asked to deliver on metrics that did not make sense, that were counterproductive to the team's effectiveness, or that were seemingly impossible to collect? Often times, the metrics being collected are the ones that are easy, but not necessarily the ones that matter. In some cases, metrics can even have a demoralizing or counterproductive effect on the team!
When it comes to software delivery, lean and agile practices and methodologies have clearly taken the lead. In the spirit of Kaizen, this session will take a look at the measures we can and should collect from agile teams, why these metrics are relevant and interesting, and how we can use them to help our teams continuously improve.
Key Learnings:
Why is it so difficult to identify meaningful metrics in the software world?
What are the best types of quality focused metrics to focus on in an agile organization?
Examples of good, bad, and ugly metrics, as well as how to analyze and interpret them
That conference 2017 - Getting your Agile Team UnstuckAngela Dugan
Whether you've been working on an agile team for 6 months, or 6 years, the same obstacles tend to arise to trip us up over and over. Maybe your retrospectives feel more like a funeral and no one is participating anymore, your daily stand-ups have bloated into 25 team member status meetings, or your QA team is falling farther and farther behind the agile developers and feel like they’ll never catch up with their testing backlog. These are the kinds of issues I see all of the time. They lower team morale, lead to abandoned transformation initiatives, and ultimately your product and customers suffer because of it. But there’s a better way!
As an agile coach and consultant, I have worked with dozens of teams to stop the bleeding, strengthen their relationships, mature their processes, and help them grow into high functioning agile machines. And to be clear, I’ve made mistakes as well! I’d like to share with the audience my own experiences and lessons-learned, including both what succeeded and what failed in hopes to lead you down the path to getting your own team “unstuck”.
Visual Studio ALM and DevOps Tools WalkthroughAngela Dugan
If you're considering moving to Team Foundation Server or Visual Studio Team Services, this deck will walk you through the highlights, of which there are a TON!
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
4. AGENDA
What reporting options are available?
Built-in
Excel
SSRS
What reports come out of the box?
Creating your own reports
5. REPORTS BY TEMPLATE
Tasks
SCRUM
Agile
CMMI
Monitor bug activity, reactivations, and trends. Track bugs that the team is finding and the progress that the team is making toward fixing them.
•Bug Status Report
•Bug Trends Report
•Reactivations Report
•Bug Status Report
•Bug Trends Report
•Reactivations Report
Monitor build activity, success, and trends. You can use build reports to track the quality and success of your team's builds over time.
•Build Success Over Time Report
•Build Summary Report
•Build Quality Indicators Report
•Build Success Over Time Report
•Build Summary Report
•Build Quality Indicators Report
•Build Success Over Time Report
•Build Summary Report
Track project health, team burn rate, and task completion.
Use to review the level of effort that the team has spent on each requirement type work items that the team is implementing. By using this report, you can quickly determine whether any work was recently completed on each item,what work is remaining and how far each item has been implemented and tested.
You can review this report daily or weekly to monitor the progress of the team during an iteration.
•Release Burndown(Scrum)
•Sprint Burndown(Scrum)
•Velocity (Scrum)
•Burndownand Burn Rate Report (Agile)
•Remaining Work Report
•Status on All Iterations Report
•Stories Overview Report (Agile)
•Stories Progress Report (Agile)
•Burndownand Burn Rate Report (CMMI)
•Remaining Work Report
•Status on All Iterations Report
•Requirements Progress Report (CMMI)
•Requirements Overview Report (CMMI)
Determine added work. You can use the Unplanned Work report to determine how much work the team added to an iteration after it started.
•Unplanned Work
•Unplanned Work
Monitor testing activity. You can use the test reports to track the team's progress toward developing test cases and to determine how well they cover the requirement type work items.
•Test Case Readiness Report
•Test Plan Progress Report
•Test Case Readiness Report
•Test Plan Progress Report
•Test Case Readiness Report
•Test Plan Progress Report
6. SCRUM -RELEASE BURNDOWN
Understand how quickly your team has delivered backlog items and track how much work the team must still perform to complete a product release.
Review the report to determine the progress that your team has made in a release and to answer the following questions:
How much work remains in the release?
How quickly is your team working through the product backlog?
7. SCRUM -SPRINT BURNDOWN
Displays the following pieces of data:
The Ideal Trend line indicates an ideal situation in which the team burns down all of the effort that remains at a constant rate by the end of the sprint.
The In Progress series shows how many hours remain for tasks that are marked as In Progress in a sprint.
The To Do series shows how many hours remain for tasks that are marked as To Do in a sprint.
Review the report to determine the progress that your team has made in a release and answer the following questions:
How much work remains in the sprint?
Is your team on track to finish all work for the sprint?
When will your team finish all work for the sprint?
How much work for the sprint is in progress?
8. SCRUM -VELOCITY
Based on the velocity of previous sprints that the report illustrates, you can:
Track how much effort your team has reported as complete for each sprint.
Estimate how much backlog effort your team can handle in future sprints if your team composition and sprint duration stay constant.
Review the report to determine how much progress your team has made and to answer the following questions:
How much effort has your team completed in each sprint?
What is the maximum velocity of your team?
What is the minimum velocity of your team?
What is the average velocity of your team?
9. AGILE -BURNDOWN
You can use this report to answer the following questions:
Is the team likely to finish the iteration on time?
Will the team complete the required work, based on the current burn rate?
When can the team finish the current iteration?
How much work can the team complete in the available time?
How much work does each team member have?
How fast is the team completing remaining work?
Is the team adding work during the iteration? Is there scope creep?
How is the work distributed across the team?
10. AGILE –REMAINING WORK
Number of Hours vs. Number of Work Items
Review the report to determine the progress within an iteration or over time. Specifically, you can find answers to these questions:
How fast is the team burning down remaining work?
Is work being added during the iteration? Is the team expanding the scope of the work?
How much progress can the team make in the available time?
Approximately when can the team finish the work?
Is too much work in progress?
Is the flow of work being impeded or blocked?
When will the team finish the current iteration?
11. AGILE –ITERATIONS STATUS
This report displays the following information:
Stories Closed: number of user stories that have been closed; derived from the current values specified for the iteration and the state of each user story.
Progress (Hours): represents the values for Original Estimate (grey), Completed (green) and Remaining (light blue) based on the rollup of hours that are defined for all tasks; derived from the current values that are specified for the iteration and the hours for each task.
Bugs: representation for all bugs, grouped by their current states of Active (blue), Resolved (gold) and Closed (green); derived from the current values that are specified for the iteration and the state of each bug.
12. AGILE–ITERATIONS STATUS
Review the report to determine how many stories are ready to release and to better understand the rate of the team's progress. For example, you can find answers to the following questions:
Did the scope of work for each iteration closely match the team capacity?
Does the number of stories closed in each iteration correspond to your expectations?
Is the team resolving and closing more bugs with successive iterations?
How many stories can the team ship today?
This is BAD!!!
13. CMMI–BURNDOWNAND BURN RATE
Burndownshows the trend of completed and remaining work over a specified time period.
Burndown
How fast is the team completing remaining work?
Is the team adding work during the iteration? Is there scope creep?
How much work can the team complete in the available time?
When can the team finish the work?
When can the team finish the current iteration?
14. CMMI–BURNDOWNAND BURN RATE
Burn rate provides calculations of the completed and required rate of work based on the specified time period.
Burn Rate
Is the team working quickly enough to finish the remaining work on time?
Work Assignment
How is the work distributed across the team?
Should the team balance the remaining work load?
15. CMMI–REMAINING WORK
Number of Hours vs. Number of Work Items
Questions That the Report Answers
Review the report to determine the progress within an iteration or over time. Specifically, you can find answers to these questions:
How fast is the team burning down remaining work?
Is work being added during the iteration? Is the team expanding the scope of the work?
How much progress can the team make in the available time?
Approximately when can the team finish the work?
Is too much work in progress?
Is the flow of work being impeded or blocked?
When will the team finish the current iteration?