We really won't know the official answer until Friday. That's when we hold this sprint's review meeting, and where the Product Owner officially accepts or declines each of the work tasks.
Speaking of tasks, if you'll look at the final point in the sprint burn-down, you will see there are a few hours—a few tasks—not yet complete.
Let's take a closer look...
We've got approximately 9 hours remaining, and most are finishing up tasks related to acceptance testing. That's right—like all of the sprints prior—our goal is to deliver the next release with no known defects related to this month's work.
Within the last 30 days, the team lost a veteran Application Developer and a veteran Quality Assurance Engineer, and we've had four people out during the month due to illness, but the team still managed to deliver more this sprint than any before. I would call that a success.
As for our goal of 90 percent of our customers being able to schedule Envision upgrades to EnvisionConnect after July 31st, John Jensen's crew has actually already begun scheduling them.
John Stender said this week that he and Geoff Marsh are considering sending a team of Sacramento inspectors to shadow the forty using EnvisionConnect in the field at San Bernardino County, and even Nick Reyes at Orange County is wondering: "Could we get along without Site Remediation for a few months?"
If these folks can begin plans to move from Envision to EnvisionConnect, anyone can. From that perspective, we may have surpassed the 90 percent goal.
Of my team, I have never been more proud!
2 comments:
Let's not forget the Scrum Master that helped to get us there, and removed our obsticles, HL, and the clients, SBCEH for example, that understood and were so patient with us while we reached our goals and worked to resolve their issues.
In case you were holding your breath... the Sprint Review just finished with a cheer and applause and the official designation of Successful!
Post a Comment