Vaca-tchemups
Nov. 9th, 2019 06:18 amFor those who aren't familiar with the term, a "sprint" in software development is a period of time in which new features are added and bugs are fixed, and at the end, everything's deployed together. When it used to just be me and one developer, it was easy; he'd send me a list of things he'd accomplished, I tested to make sure it was all good, we scheduled a deployment, and I wrote release notes. But our work was well-received and more groups wanted to have tools built for them, so the whole project has grown. I support three developers and we use a Visual Studio board to keep track of everything, which is essential because the sprints keep getting bigger and lasting longer. And I guess I prefer that because we were on a two-week schedule, which was too quick.
But I'm only mentioning it because the last sprint got pushed back as far as it possibly could. I feel like I sent out release notes, published documentation for the new tool, then shut off my computer and got on the plane for our vacation.
(full vacation photo album here)
( More... )
But I'm only mentioning it because the last sprint got pushed back as far as it possibly could. I feel like I sent out release notes, published documentation for the new tool, then shut off my computer and got on the plane for our vacation.
(full vacation photo album here)
( More... )