@nibor, you are completely right, the team should plan the sprint for these situations to be prevented. I could point out that the story was not discussed during planning, reqs are missing, no definition of done, etc. I sometimes do. But people may go into defense mode and we all start discussing why someone is right or not. In this case I got the opportunity to get the message across by just posing some innocent questions. Which was quite entertaining for me, and I am sure the SM is cautious to avoid the loophole in the future :) We are agile though, just polishing the rough edges still.

Consider a position at the interconnection of IT and Business departments? Large companies maintain a multitude of inefficient processes which they happily hand-over for automation. Beware process redesign, battling Excel dragons, dealing with business counterparts may be frustrating from time to time. Coolest part is you are considered a true hero once a process is automated. ++ for making this visible in a BI dashboard. Some solutions that come to my mind:
- RPA (Uipath, AA, BP)
- Python, .NET
- App developement (Mendix)
- Integrations (Mulesoft)
- Workflows
- SAP automation
- Tibco Spotfire, Power Bi

@junon, @Root,

Thanks for the thumbs up, with the new avatar I am definitely in for a great time here!