Azure task board9/17/2023 ![]() The SCRUM Template in Azure Boards supports some Work Item Types (WITs) that don’t fully align with the Scrum Guide. The cool part about Agile is that it encourages learning and experimentation which is what are at the very heart of this project. Depending on how this goes, I might end up combining the two. Since I’m both the Scrum Team and the product owner, a Sprint Review will look very much like a Sprint Retrospective. This review occurs before the next planning session. Sprint Retrospective - The Sprint Retrospective is a short meeting where the Scrum Team reviews what worked and where things can improve in terms of the framework. Sprint Review - In this meeting, the Scrum Team shows the product owner what is “done.” The product backlog can be cleaned up and there’s a discussion of what went well, timelines, budgets, and what to do next. Timeboxing it at 15 minutes prevents too much reflection. Every day should start with centering on where you’ve been and where you wish to go. While this works well in a group setting, I can see it working equally well with a single contributor. My Sprint is set for a week, so my Sprint Planning session will take no more than 2 hours (assuming it’s 2 hours per 1 week in a Sprint).ĭaily Scrum - The Daily Scrum is a 15 minute morning session where the previous day’s activities are reviewed, the current activities for the day are decided upon, and any impediments are listed and considered. The Scrum Guide says this should be about 8 hours for a 1 month long sprint. Sprint Planning - Sprint Planning is a time boxed activity where the list of to-do items is created. “Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.“ ![]() Since I’m the only bottleneck for my own issues, I’ll give myself 1 week deadlines. I don’t need to ask permission of anyone, nor do I need to wait for other groups to provide resources. I can’t say that that’s an industry guideline, but for most enterprises, that seems an OK duration. The Sprint Guide recommends making the Sprint 1 month or less. The Sprint - The Sprint is the amount of time given to get something “done.” This usually means you’ve made something useful. I’ll adapt those events to suit my work style. Scrum practitioners use a few different events during the course of a project. There are multiple Scrum and Scrum Master certifications. ![]() But as I stated in part 2, this is more of a way for me to reinforce what I learned in my Certified Scrum Master course, than an exercise in pure practicality. I’ll admit that it’s a bit odd to apply a team based approach to development like Scrum to a 1 man project. Before I begin to add items to the board, it’s important to decide on the events and cadence of the project. ![]() In Scrum terms, I’m both the Product Owner and the Scrum Team. I’ll also describe a little more my approach to Scrum as I’m both the customer and the developer. This article will dig deeper into adding tasks such as Product Backlog Items to the board. Part 2 discussed choosing a work tracking mechanism and code storage solution. I’ve laid out some of the basics in two previous articles. I also gain insights into methods of hosting the app locally and in the cloud on a variety of platforms - vms, containers, serverless, etc. I’m sure that apps like this already exist, but by writing it myself I’m able to get my hands dirty and see what works and what doesn’t in terms of DevOps tooling and techniques for smaller projects. This app that I build will track our progress. We then decided to make it more fun by running a race in each of the 50 states. My wife and I decided a couple of years ago to visit all 50 states. I’m working on a project that will allow me to put some Agile and DevOps skills to use by writing a small app that I’ve had in mind for a while now. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |