![v ] µ ] } v o & u Á } l } ( Z v ] r } µ ] } v } u u ] } ( Z W o ] u v ......W } o ] Ç ] ( ^/ v ] µ ] } v o & u Á } l } ( Z v ] r } µ ] } v } u u ] } ( Z W o ] u v } ( D }](https://static.fdocuments.us/doc/165x107/5f7117e4e9dcaf79a54a145b/-v-v-o-u-l-z-v-r-v-u-u-z-w-o-u-v-.jpg)
Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ]...
8
White Paper FRESHER VIEW ON KANBAN AND TESTING. Abstract: In this article we present practices that many of our customers use when implementing a Story or high-level requirements during a sprint or in a flow-driven delivery. This is different from the usual Kanban board, sequencing the various development stages (Ready, in analysis, in dev, in test, done). Those customers need or prefer to add rigor into their delivery flow to augment the quality of their products and solutions. While this approach cannot be used universally, we found that this is quite efficient in some case, especially when tooled with XStudio™.
Transcript of Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ]...
![Page 1: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/1.jpg)
White Paper
FRESHER VIEW ON KANBAN AND TESTING.
Abstract: In this article we present practices that many of our customers use when implementing a Story or high-level requirements during a sprint or in a flow-driven delivery.
This is different from the usual Kanban board, sequencing the various development stages (Ready, in analysis, in dev, in test, done).
Those customers need or prefer to add rigor into their delivery flow to augment the quality of their products and solutions.
While this approach cannot be used universally, we found that this is quite efficient in some case, especially when tooled with XStudio™.
![Page 2: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/2.jpg)
2
INTRODUCTION
There are many books and many more videos addressing the “how to deliver using a Kanban style board”. This has brought a lot to the software industry when used by teams that were ready to adapt it to their context. Adaptation can take different forms.
One of our customer stated: “Working with Kanban is like creating a tiny waterfall! If you look at it from a high-level, this is about sequencing waterfall tasks at low granularity! In our organization, we do not have senior, highly experienced developers… we must MAKE them. So, we need to be much more rigorous and drive them more.”
So much for agility and flow-driven development… the “Empire strikes back”. Well… this is not so. It turns out this customer, as others we found later, does use Kanban board, in a very efficient way for its context.
This paper relates how this customer adapted and how XStudio™ helped him in doing so.
A USER STORY, ANY STORY, IS A SET OF PREDEFINED TASKS
A Story is basically a high-level functional or technical requirement for your solution. It expresses a desired capability and how the users or system will probably use them.
Figure 1 : developer tasks for a story
![Page 3: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/3.jpg)
3
When a development team addresses a story, there is a set of tasks that a developer MUST do:
Understand the need: read the story, get a direct conversation as close to the end-user as possible, rephrase, draw, until you can…
DESIGN SOME TESTS TO CHECK THE STORY BY YOURSELF: design at least a positive test, a negative test, but don’t try covering all test cases. The goal here is to make sure you really understand the need. If you can’t write useful test (automated or manual), then you are clearly not understanding the need and you must iterate to the “understand the need” task
Make your impact analysis and design: this is time when you need to ensure you know which code, which files and artifacts you should check out, which classes, methods, you need to alter or create… and resolve contention with your peers about the data model, should you need to adapt it
CODE AND UNIT TEST: this is the time when you create or adapt the code, the configuration parameters, the artifacts… There you can get several short tasks – You need to ensure the highest quality and coverage by writing and exercising independent unit tests
RUN YOUR FUNCTIONAL OR TECHNICAL TESTS: use the test you defined earlier to make sure what you implemented is working and answers the need your understood
Code review: get one of your peer to review your code – don’t let “code smells” go through – (re)factor your code now… get back to “Code and Unit test” task if needed
Build and SMOKE TEST on your sandbox environment: before you commit anything, make sure it builds and hasn’t broken anything major
Commit and let continuous integration run Watch for automated feedbacks and take corrective actions: if your solution benefits
from automated tests and code analysis, you should get rapid feedback, which is easier and faster to correct while you are still immersed into the functionality you developed
DRIVE SOME EXPLORATORY TEST AND DEMO: If you are experienced enough, just do it, or in pair with a Business Analyst or a SME
and iterate to whatever corrective action
One can say that this is an evident set of tasks any professional developer shall deliver on. Probably… but for many companies, professional developers are not the norm. Many “freshers”, out of schools are to be trained before they can be productive, especially in an Agile project.
![Page 4: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/4.jpg)
4
A STORY, IS THEN DELIVERED ONE TASK AT TIME
The above model can be adapted to any context. What is important for agile project favoring visual management, is how you then make progress and blockage apparent for quick resolution.
You can then use a very simple Kanban driven flow, for each task:
In progress Blocked Done
That’s it.
Figure 2 : Progressing tasks for a story
![Page 5: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/5.jpg)
5
You drive your tasks for a specific story, one at a time.
You keep the advantage of managing Work-in-Progress limits: You can’t have more tasks “in progress” than you have makers in the team You can’t take a new task on a user story if the prior is blocked All blocked task is immediately made apparent, and you can address it without even
waiting for the daily stand up
Figure 3 : progression the stories
![Page 6: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/6.jpg)
6
QUALITY IS BUILT DURING THE DEVELOPMENT, NOT VERIFIED AFTER
As you noticed there are multiple task devoted to test in this micro-process. Nothing if new here. It is just to that you give the habit for the “developers” to do them.
During this process XStudio™ is used all along.
The functional or technical tests are defined and designed in XStudio™. This can be manual or automated test. There can be shared with a QA team, so that they don’t have to retry them, there can be used later as smoke test. They can be used by the business analysts or the SME to make sure you understand the needs; they can be used for Sprint review demonstration …
The unit tests can be SCANNED by XStudio™ and uploaded to be used in regression campaigns on the integration environment. XStudio™ greatly facilitates the management of those unit tests avoiding the developer to describe each and any test. Results are extracted from the standard outputs format of any xUnit compliant test framework.
Smoke tests and regression campaigns are easily defined based on the tests that have been created during the development.
Exploratory tests are used to ensure the quality of new features for which you may not have the time to create automated tests during the development – note that many customers prefer to manage test automation as stories on their own, applying the above process.
With XStudio™ you can turn exploratory test notes as manual scripted test using the PDNL automatically.
If you are stringent on quality assurance you can also manage your code review as test and use the defect module to follow on code review defects.
XStudio™ is used during all your development process. It allows building and measuring quality as you go. You can know deliver more easily on your test pyramid, and with efficiency.
![Page 7: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/7.jpg)
7
Figure 4 : Test pyramid
SUMMARY
NOT ALL SOFTWARE ORGANIZATION ARE EQUALS WHEN IT COMES TO AGILE DELIVERY. SOME ADAPT AGILE
PRACTICES TO MATCH THEIR CONSTRAINTS: USING AN EFFICIENT FLOW-DRIVEN DELIVERY, MATCHING THEIR
DEVELOPERS’ LEVEL OF EXPERIENCES AND ENFORCING QUALITY ASSURANCE PROCESS.
XSTUDIO™ IS VERSATILE ENOUGH TO ACCOMPANY SUCH PRACTICES, WHILE PRESERVING ALL THE QUALITY
ATTRIBUTES OF AGILE METHODS. TESTING IS AT THE HEART OF ANY EFFICIENT SOFTWARE DEVELOPMENT TEAM. GETTING XSTUDIO™ AS YOUR CORE TEST MANAGEMENT TOOL WILL TREMENDOUSLY ACCELERATE ADOPTING THOSE
PRACTICES.
![Page 8: Fresher view on Kanban and testing- rev 1 · î /EdZK h d/KE d Z u v Ç } } l v u v Ç u } À ] } ] v P Z ^ Z } Á } o ] À µ ] v P < v v ï t Z v À o } u v u } Ç U Z ] } ( l Z](https://reader033.fdocuments.us/reader033/viewer/2022042910/5f416bbc88e57b7e3824de49/html5/thumbnails/8.jpg)
8
XQUAL: THE TESTS ORCHESTRATION SOLUTION
XQual™ delivers XStudio™, a versatile management and orchestration test solution, supporting over 80 test automation frameworks, allowing fully distributed and scalable test execution. Since 2008, XQual is solely focused on inventing, designing and delivering smart solutions for the most demanding test practitioners.
XQual / Gavaldo Consulting Cidex 436 chemin des Tourres 06330 Roquefort les pins FRANCE
http://www.xqual.com/
![W } u } ] v P Z t o o v } ( D ] v U } Ç U v ^ ] ] d Z } µ ... · u v'E U , u ] o } v :W U ] o Ç ' X d Z ] u } ( v µ Æ ] v } v Z µ u v } P v ] ] À ( µ v ] } v v u v o Z o Z](https://static.fdocuments.us/doc/165x107/5ec211d2f5ec2c6a585c32a1/w-u-v-p-z-t-o-o-v-d-v-u-u-v-d-z-u-ve-u-u-o.jpg)
![E ] P Z ^ Z ] ( t } l / v Z Z ] l } ( Z u D ] } v Z: U Z ] ,^ U ^ Æ v Z U ^ Z & … · E ] P Z ^ Z ] ( t } l / v Z Z ] l } ( Z u ... tZ ] t o o } u / v À ] P } t o o } u d µ ~](https://static.fdocuments.us/doc/165x107/60e0bb97dc9b9e5c250defbc/e-p-z-z-t-l-v-z-z-l-z-u-d-v-z-u-z-u-v-z-u-z-.jpg)
![E ] } v o v } v ] Z ( v À o } u v o ] ] o ] ] µ ] u^ µ u ... · } ] ] } v Á v ^ v ] v r P v v Ç ] v À o. d u ] Z U ^ Á ] Z Z ] P Z À ] Ç } Further analyses indicated associations](https://static.fdocuments.us/doc/165x107/5c02669d09d3f2ab198b65fe/e-v-o-v-v-z-v-a-o-u-v-o-o-u-u-v-a.jpg)
![W o , o Ç } µ ( } ^ o ( r/ } o } v ] vt l K v vd Z Y µ ] Ì · v } Z À Ç Z } . o u U Z ] u Á ] Z } µ Á } µ u } v v P Z } ( / } v v ] s o Ì l ] U Z u ] v v ' l Z o ] X](https://static.fdocuments.us/doc/165x107/5ed149cea225a048a515d75e/w-o-o-o-r-o-v-vt-l-k-v-vd-z-y-oe-v-z-z-.jpg)
![µ ] v ] P W u ] µ ] v K v o ] v ] · 2020-04-10 · } ( Ç } v À Ç u o Z ] U } Z v P u U µ Z Z v P } } o o u } µ v U ] v ] } v } µ v U X](https://static.fdocuments.us/doc/165x107/5e9eaf30611d0809500fb728/-v-p-w-u-v-k-v-o-v-2020-04-10-v-u-o-z-u-z.jpg)
![~ ' } À v u v } ( D Z Z v ] } ( , v ] Z Z } ( u Ç ^ } W ] u ' } À …...~ ' } À v u v } ( D Z Z v ] } ( , v ] Z Z } ( u Ç ^ } W ] u ' } À X , ] P ... ... K v](https://static.fdocuments.us/doc/165x107/5e8a074c03ac1b2a630583b7/-v-u-v-d-z-z-v-v-z-z-u-w-u-.jpg)
![E z z z z - Unicode> K>>/E^ s ] v u E ( o ] Æ U / v X d Z v Z E Z v E'N s ] v u Ezh > ] v P µ ] ] ^ ] v P W } i D X < v > µ v U > ] v P , ] U t µ d l P ] U](https://static.fdocuments.us/doc/165x107/5f5a37d4642d3f16b654ecd3/e-z-z-z-z-unicode-ke-s-v-u-e-o-u-v-x-d-z-v-z-e-z-v-en.jpg)
![Æ v u v } ( Z } ] o ] u } ( Z P µ ] } v } ( v P o Z ( } u Z P } Ç ......^ ] } ( Z } u u ] ( } À o } u v W } o ] Ç U h v ] E ] } v u v ( } } v } u ] v ^ } ] o ( ( ] U í U î ì](https://static.fdocuments.us/doc/165x107/60abf540d41fca44cc46e0de/-v-u-v-z-o-u-z-p-v-v-p-o-z-u-z-p-.jpg)
![u } ( ] } ] v ] } ] W u } ( Z , µ u v' µ } v v } Z u } Z P ] Z ] Z ] } o ......^ ] P v ] ( ] v ] o P } Á Z ] v Z i i µ v µ u v ] o µ u U u } o Ç ] v Z ] o Z } µ o o X U W](https://static.fdocuments.us/doc/165x107/5fe8f78cb53138045e647015/-u-v-w-u-z-u-v-v-v-z-u-z-p-z-z-o-.jpg)
![The Translators to the Reader · K v h v ] ( } u ] Ç } ( W Z ] v P v } Z Z ] v P Á Z ] v l P } } } u } v ] Z Z } ( ~ P v o Z Z Á K v h v ] ( } u ] Ç } ( W Z ] v P r Æ u o ·](https://static.fdocuments.us/doc/165x107/5f14ea764296f15d5e78f92e/the-translators-to-the-reader-k-v-h-v-u-w-z-v-p-v-z-z-v-p-.jpg)
![æ á z x x z x x z - Eiger Design...À ] } v ] hhd Á Z ] Z Z À µ o U µ v v U } u u µ v ] ] } v µ X Z Z/E ð î õ v ] À Z ï î v u ]](https://static.fdocuments.us/doc/165x107/5f76324c5f12f159f479efd2/-z-x-x-z-x-x-z-eiger-v-hhd-z-z-z-o-u-v-v-u-u.jpg)
![^ Ç v Z ] v ] } Ç v Z ] ^ µ ] } v Ç } u ] ] v - Thieme^ µ } Ç ^ Ç v Z ] v ] } Ç v Z ] ^ µ ] } v Ç } u ] ] v ^ µ ] ] Á X D Z U E ] Z } o Z X > U D Z Á : X Ç v U > ] r](https://static.fdocuments.us/doc/165x107/5fa2e64833b1b02ce7147fc7/-v-z-v-v-z-v-u-v-thieme-v-z-.jpg)
![&>h/ E > dZK>zd > E r r î · 2020. 4. 12. · u ] v v v v o u v d Z Ç X / v W Z u v Z U < o ] P u v Z U : v } v , U ] } X E o } v Æ } } l } ( ] ] X í ó Z ] ] }](https://static.fdocuments.us/doc/165x107/5fc40ddc9f211a7e5e54d61e/h-e-dzkzd-e-r-r-2020-4-12-u-v-v-v-v-o-u-v-d-z.jpg)
![o E v } o Ì u v v D Z ] v · 2021. 3. 5. · d Z , o u Z } o Ì & v P Ç } ( ^ Ç u Ç u Z o ] ( ] u µ v v o Ç À Ç ] v P Z Á Z ] Z ] À ] ] Z À ] } µ U }](https://static.fdocuments.us/doc/165x107/6117f9be3785f80bcd0d85f2/o-e-v-o-oe-u-v-v-d-z-v-2021-3-5-d-z-o-u-z-o-oe-v-p-.jpg)
![s } o o Ç rd µ Z h ] l W } À ] v ] o l u t rs o v v · 2019-09-10 · Z t ] u s v o Z u U } Z À v s W r< Ç D v v U Z D À o ] P U } Z À v sd < } ] i l U Z : } Z v s v Z ] U](https://static.fdocuments.us/doc/165x107/5e9d588cd0c2f172572828ed/s-o-o-rd-z-h-l-w-v-o-l-u-t-rs-o-v-v-2019-09-10-z-t-u-s-v.jpg)
![v / v À ] } v ( } u Z &h Z Z v } u u ] © Z ]114 Hair Transplant Forum International May/June 2016](https://static.fdocuments.us/doc/165x107/611e1ba946fbb755c47d081f/v-v-v-u-z-h-z-z-v-u-u-z-114-hair-transplant-forum-international.jpg)
![] o ] u Wnhssp.org.np/Resources/PPFM/eGP_Standard_Operating... · ] o ] u W d Z ] u ] o Z v ( µ v Ç h< ] ( } u Z h< P } À v u v V Z } Á À Z À ] Á Æ } v }](https://static.fdocuments.us/doc/165x107/5d19d5b388c993a85b8d8b35/-o-u-o-u-w-d-z-u-o-z-v-v-c-h-u-z-h-p-a-v-u-v-v-z.jpg)
![K ( ( ] } ( Z } u u ] ] } v ( } v v Æ u ] v ] } v U d Z ...€¦ · K ( ( ] } ( Z } u u ] ] } v ( } v v Æ u ] v ] } v U d Z ] µ À v v Z µ u](https://static.fdocuments.us/doc/165x107/5f0269a77e708231d40426b6/k-z-u-u-v-v-v-u-v-v-u-d-z-k-z-u-u.jpg)
![v o o ] v P ^ Z ]... · 2020. 6. 16. · Z ] À X < ] v Z P E ] } v o W l U Z } u } Z D v ] v > l Ç u Á v Z l Z ] u } Z v ï U ï ï ì](https://static.fdocuments.us/doc/165x107/60f8d9e7d89658779873bc29/v-o-o-v-p-z-2020-6-16-z-x-v-z-p-e-v-o-w-l-u-z-.jpg)