Scrum Retro – Forgetful – Mailbox

So you are on a Scrum team that performs retro’s at the end of an iteration\sprint.  And during the beginning of these retro’s, everyone ponders (or tries to remember) what went well and what didn’t go so well.  Pretty common issue for many Scrum teams.

Possible Solution – Setup a Scrum mailbox that team members can drop notes into during the iteration.  Place the mailbox by the morning Scrum location for easy access.


Agile Testing Pyramid

If you have ever developed a build\deployment pipeline with automated UI testing at the end, then this article is for you!

Its spot on with how fragile UI tests can be and the amount of $$$$ it cost to keep maintaining them.

So in a nut shell, this is what I am taking away from the article in regards to testing strategies.  (#1 below is given the most priority, with #3 given the least)

  1. Focus most of your testing on unit testing.  Really get your developers to put effort into building out unit tests and make sure they are executed with every build.
    • Failed unit tests = failed builds
    • Automate everything!!!
  2. Next, try to test services individually via automation.  An important aspect here is that the UI shouldn’t contain service\logic features, but just UI controls that call back into the service.
  3. Finally, the UI testing that seems to always need maintenance should be given the least amount of attention.  Something that still needs to be done, but your focus should not be here exclusively.


Interesting article….  Seems like back in the waterfall days the focus was on finding bugs, but now with agile, the focus is on preventing bugs…

My vote is for Agile! 🙂

Certified ScrumMaster

Early this year I took a ScrumMaster training course and then obtained the certification.  Overall I thought the course and instructor were very good.

Some of the key items that I took away from the class were as follows.

  • Importance of team retro’s
    • Because my team had been doing Scrum for so long, we kind of did away with retro’s.  I guess this is not out of the norm for mature teams.  Bottom line here is we started doing retro’s again.
  • Change is really ok and periodic change can be even better!
  • It is ok to carry stories over to the next sprint.
    • The sprint were the work is completed is the sprint that gets credit for the work
  • During morning Scrum’s, the team should really not speak directly to the Scrum Master, but rather the entire team
  • Add a “fun” element to the morning Scrum
    • Trivia
    • Dice shake
    • etc…
  • Only try to fix 1 item from the retro.
  • Know the 4+ Scrum meetings as it could be a test question
    • Sprint Planning (What and How)
    • Daily Scrum
    • Sprint Review
    • Spring Retro
    • Backlog Refinement (Unofficial)
  • Context switching between multiple project just doesn’t work…..

There were many other items, but those are the ones that stand out.

The certification test wasn’t bad as long as you paid attention in class. 🙂


Starting my blog…..

Starting up another blog.  My previous blog was on and ran for about 7 years.  Lots of good stuff, but time for a change, so I decided to try

Some of the DevOps topics and tools I will be blogging about are.

  • DevOps
  • ELK
  • Docker
  • AWS
  • Gradle
  • Ant
  • Maven
  • Ansible
  • TFS
  • Git\GitHub
  • Jenkins
  • Java
  • Spring Boot
  • Scrum
  • Monitoring
  • etc…..