Journey to Effective Reporting - Make the Impact!
Fortunately, nowadays, we have tools that can provide us with dozens of reports in seconds and we can measure and visualize almost everything. But every coin has two sides. We often forget what is the purpose of reporting, why we do it and what impact we want to make. We just generate and deliver dozens of charts, tables, numbers but …
… nobody reads …
… nobody understands …
… nobody cares …
and most importantly – there is no impact. I would like to share with you how to avoid such wasting following “simple” steps applicable to any reporting to give you clues how to make a real impact.
Agile Drawing - Game
We all live in the Agile world, and most of our projects are Agile, or we are on our way there.
However, we often forgot about the fact we are only humans, and as humans, we have feelings, emotions and these are very important, may be more important than the rational part of us.
I will play a game with you to show you several situations we are all familiar with, and I would like to analyse how do you feel in these situations and what should we care about to understand how to make our Agile projects easier and us happier.
This workshop does not require any special drawing skills and I promise you it will be a lot of fun. The only requirement is you need to cooperate with me and play the game.
Also, you can then play this game with your teams later to take it in the context of your situation.
Power of Mind Maps in Agile (QA) (синхронный перевод)
"Working software over comprehensive documentation." - is written in Agile Manifesto and it is dogma we all believe in, and I am not an exception.
However, the wording is "over" not "instead of". It means we value the left side more, but there is still value on the right one.
Documentation is significant, even in Agile. We, as QAs, have to produce quite a lot of artifacts
We all use some very good tools to manage our development like Jira, Rally, etc. These tools are perfect for requirement management, work planning + tracking, defect tracking and many other activities.
But I am often struggling using them freely when I found out they kill mine creative thinking and limits my results. I need something more in addition to stories, tasks, defects and all other entities.
I love mind maps for all of these. I would like to share with you why and how I am getting the most benefits from mind mapping approach. I will also share many templates you will be able to download.
Test Cases - are they dead?
Test Cases are as old as functional testing is. They are powerful artifacts but also possibly the biggest source of time and money waste in test industry.
Do we need them at all nowadays? In world of Agile, automation, continuous everything? I do not think so… BUT!
Everything said before the word “but” does not count. True…
From Scrum to Kanban – what does it mean for QAs?
After years doing Scrum, or to be precise, trying to do it - with many wins but also many failures, we are slowly moving to Kanban. Why and how? What does it mean for QAs? Let me share our story with you.
I will share with you why the Scrum was our first choice. How we implemented it and what challenges we had. I will explain reasons why we switched to Kanban later and how we actually did. I will provide you with Guide for such transition and we will have a time for discussion.
Talk will be focused on concept of “Quality as responsibility of whole team”.
Visualization of Quality (Effective Reporting) (синхронный перевод)
QA in Agile is far behind testing - it is more about:
- Assuring delivery of real business value…
- ... In expected quality…
- ... Based on proper requirements…
- ... When all stakeholders are satisfied…
- … And everybody enjoys it!
QA as responsibility of Whole Team (синхронный перевод)
Agile team is the group of different people, roles and individuals, but we all share the same goal=Deliver real value and enjoy it
There was an idea that quality equals testing and only testers are responsible for it. Of course it is not true and Agile cleared out that testing itself is only measurement and it does not bring any quality itself. You cannot test Quality in;you need to build it in
If Quality is understood as“Satisfaction of all stakeholders”than it needs to be responsibility of all of them. Each role and team member needs to contribute from its point of view and collaborate with others. Testing is still very important but it is only small piece of puzzle called Quality Assurance.So what are the other pieces?
I would like to share with you what is my vision of QA journey through the project life cycle, what the pieces are, how to bring them together, where to start,who is responsible for what and what achieve the point when whole team is responsible for Quality