The Scrum Alliance has announced this week at the 2018 Global Scrum Gathering in Minneapolis that it now has a partnership with Jeff Sutherland's (the co-founder of Scrum) Scrum@Scale. I look forward to teaching and helping teams embrace Scrum@Scale over other prescriptive techniques.
I get often asked when I work with people or teach a class how to show real progress on an Agile project. Roadmaps, Release Burnup's, Velocity, how to answer questions on delivery. We build products for external clients using Scrum and will show people how we visualize progress sprint by sprint for our customers. Showing how velocity changes, roadmap, release plan changes and most importantly how customer feedback has affected the release date. This isn't hypothetical talk but real world experiences and conversations.
However, first I will start out with showing the old ways of doing things with Gantt charts. Why the traditional way doesn't work. Comparing the Green, Yellow, Red method and how it doesn't work. The roll that into the better, agile mindset of delivering questions like when will be done, what will we get and how we communicate good and bad news to our clients.
We often get asked what the differences are between a native mobile application and a hybrid one. I was starting to put down some notes on the topic when I came across an article that summed up my thoughts. So I wanted to go through it and mention some key points.
Scrum isn't easy, but it's effective. One of the things that teams struggle with is a way to automate their testing and learning techniques like Test-Drive Development or Behaviour-Driven Development. Both which can be implemented in both the back-end and the front-end code.
One team, I work with also automates the UI testing. One tool they use and they include as part of their Definition of Done for each feature is building a test automation using...
I just recently updated my Mac to Sierra and Xcode 8.2.1 and right away had issues connecting to the Mac using the Xamarin Mac Agent from my Windows PC. I made sure that the versions of Xamarin on the Mac and Visual Studio on the PC were the same version but kept getting the error "Xcode license must be accepted in order to be connected and working against the Mac".
This is my second real world BDD examples that we use here at Clearly Agile. I've been given permission to share this piece of code from the client.
In this example, we have a scenario where a user can create something called a "Project" and it has to have a correct "Open Date". Which is when the Project is complete.
Clearly Agile, the company I own and operate, was featured in a recent book "Best of Tampa Bay." (Page 207-211) It talks about our early days, and it's nice to be mentioned alongside other great companies and locations in the area.
Over at toggl, they have a great infographic showing how you might build a car using waterfall vs. scrum vs. kanban vs. lean. We liked it a lot that we wanted to share... There're a couple of spots I want to point that we liked that I pointed out...
In my last post I talked about Estimating, and how I don't believe in the #noestimates movement for most situations. As previously stated, for my team, not estimating is not an option.
Here you'll find some "What If" scenarios - demonstrating the clear advantages for estimating.
Lean Beer is conducted in a similar fashion as Lean Coffee. The main difference between the events is that usually Lean Coffee events are held early in the morning. Yes, you can run a Lean Coffee anytime, but it also has the downside of needing walls and the mechanics of dot voting if it is not held in an office setting.
The Professionals are organized, communicate regularly, and go above and beyond, Amateurs do not. Now, the term "Amateur" here sounds condescending, but it's not meant to be. It is a state based in two orders: the persons' mindset, and secondly, what they physically can or cannot do. This concept also extends to programming, where we encounter the two types: Amateurs and Professionals.
In addition to the Amateur and the Professional types, there is a third type, verbosely named 'the Amateur Who is Called a Professional'. This third type has four subsets that are worth mentioning.