Agile
A Fun Marshmallow Challenge Debrief
You can find a lot of praise for the Marshmallow Challenge. It is a good warm-up for workshops and training sessions and you can learn
You can find a lot of praise for the Marshmallow Challenge. It is a good warm-up for workshops and training sessions and you can learn
One of the major topics that intimidate test engineers is the No-QA question or approach (depending on your view of it).
I heard such responses after the session “Fiverr delivering fast..No QA”, by Gil Wasserman, Fiverr VP R&D, at our Agile Israel 2016 event. QA members asked me if they should look for their next role, and I keep hearing this concern whenever this topic arises.
So, is it true? Should we eliminate the QA role? Or better say – merge it into the developer’s role?
A Quick Fun Way to Understand the Basic Concept of Iterative Incremental Development A fundamental aspect of Agility is incremental and iterative development. It’s so
A big problem with a garden is that it doesn’t stop growing. And so does the scope of a software development project.
A lot of effort is invested by gardeners in fighting the growing garden. They are constantly weeding, pruning, and trimming to control how the garden looks and to make sure it best serves its purpose.
How much are you investing in weeding your scope?
There is nothing like a good long run for clear thinking and giving rise to new ideas. This post is a result of my weekend run, and it’s about managers and why it is so hard to impact their mindset in the Agile journey.
The idea originated as a result of my experience working with this company where the managers find it extremely difficult to relate to the newly formed scrum teams and instead keep communicating with their original teams (Dev and QA teams) and at the same time keep complaining about how the “scrum teams” are not accountable for their end-to-end deliveries.
When we build a kanban board to manage our work (either practicing Kanban or Scrum) we usually create a Backlog list (usually the first column) and a To Do list (following the Backlog). I’ve noticed that many times the separation between the two is artificial and people don’t always understand the critical difference between the two. I’d like to discuss it here.
One of the significant changes while moving to Agile teams is that testers and developers are now part of the same team.
This change introduces great advantages, as well as some challenges.
The immediate impact is that the testers participate in the Scrum ceremonies and get a better exposure to the product under development, its status, and its fragility. They can therefore detect better potential areas for defect finding, gain better sync for when they’ll get a drop for testing, and can better utilize their plans.
We’ve all seen it. It’s quite an elaborate show with Scrum Masters, Sprint Planning, Daily Standups, Secret handshakes, a lot of artifacts, ceremonies, roles. The recent “broadway”-level productions include bigger pictures, more roles, artifacts.
ROI/Impact of Agile Approaches Reading List rico08a.pdf (application/pdf Object) InfoQ: Return on Investment for Automated Testing The Business Value and ROI of Agile Methods –
Agile Coaching Reading List Kate Oneal | xProgramming.com Navigating Conflict on Agile Teams: Why “Resolving” Conflict Won’t Work Resources to Build Agile Coaching Competency |
Request for additional information and prices