Sprint 10 Planning

-
During this next sprint, after figuring out the basic outline of my presentation, the main thing that must get done is fixing bugs. I’m going to do a quick demo of my software during the final exam, and so stuff needs to WORK. So those are the highest priority items.

Anyway, here are the sprint backlog items:

PriorityDescriptionPoints
700Create outline for presentation.2
690Gather study materials for oral exam.1
680Fix task creation error where error message is sometimes shown though the task was created.3
670Fix blocking tasks page.3
660Fix task editing bug where the task creator can’t edit the title/desc.3
650Study for the oral exam.3
640Move the task list on the project page to the top, above the project info..5
630Make subtasks indented on the task page..5
620Make the subtask and dependent task lists further apart on the task page..5
610Put a link on the task page going back to the project page..5
600Make the default task priority “normal”.1
590”Task created” page should return to the project page or at least have the banner and a link to the project page.1
580”Task edited” page should return to the task page or at least have the banner and a link to the task page.1

This is a total of 20 hours, which I think is doable considering this weekend will be entirely devoted to this stuff. If I’m lucky I might even get more done; I do have all the remaining items estimated so I can pull stuff in if I finish all of this early by some miracle. Anyway, that’s what I’m gonna be doing all weekend!

Comments

Post a Comment

Popular posts from this blog

"Does it get easier?" Yes, but Also No...

-
Image
Image by Arek Socha from Pixabay It's complicated... "Does it get easier?" I see some form of this question asked a lot in beginner programming groups. I always struggle with how to answer this honestly and clearly, because the truth is not that simple. In some ways it does get easier, but in other ways it is almost always going to be difficult if you are advancing in your career . If you are a programmer and your job is easy for years on end, the most likely explanation is that you're in the kind of dead-end position that people try to avoid, not the kind of position people dream about when they think of becoming a developer. Most likely you are not getting better at being a dev, not working with new tech or solving new kinds of problems, not being given more responsibility, etc. etc. etc. I've seen some pushback from other newbie programmers on the idea that it could remain difficult past the initial learning stage. Notably I have never once seen somebody who...
Read more

How to Land Your First Dev Job: Develop Yourself, Market Yourself

-
Image
Image by magnetme from Pixabay In the coding and tech groups I'm in, I see the same question asked over and over by folks who are just learning to code, finishing up a bootcamp, degree, or other training program, or who have been looking for that first job for awhile and not having any luck: "what do I need to do to get my first dev job?" There's a whole ton of info out there on this topic, but it's scattered all over, so I thought I would gather together the best resources I've come across and share them, along with a bit of context, to try and help everybody struggling with or just plain wondering about this. There are a lot  of things you can do to improve your chances of finding a job and hopefully shorten your job search. They are broadly divided into 2 categories: developing yourself and your skills, and marketing yourself and your skills. Note that you don't need to do everything on this list, nor do you need to do it all at once. This is an "...
Read more

Git. The WHAT and WHY Edition.

-
Image
Lately I've seen a lot of new/aspiring developers talk about difficulties learning git . I was confused at first, because there are approximately a zillion git tutorials out there. But then I started really looking at what people were saying AND what all those tutorials contain. The problem is most tutorials start out with "here are a ton of git commands to memorize", and this is not where people are having problems. People are having problems with "what is git, why should I learn it, and what does it look like to use it in a real-life project?", and those questions are largely not answered in all those millions of tutorials. So at the risk of redundancy, I'm going to attempt to address these questions in Yet Another Article About Git. First, I want to make it clear that if you want to be a programmer, any kind of programmer, you need to know git. You just DO. This is the short version of the answer to "why should I learn it?".  The medium length a...
Read more