Sprint 9 Planning

-
Finally, on to sprint planning. I'm going to be meeting with my advisor on both remaining Mondays, so I'm going to plan these last few sprints for a week(ish) each, instead of 2 weeks. This also suits the crunched timetable. I couldn't plan last weekend as I needed to know what my advisor thought my priorities should be, and then I had a couple busy weeknights, so here this finally is.

 There are some development tasks that need doing before The End, but there are a whole lot of non-development tasks, too, and one of those is the most immediate concern. I need to get my paper for my project done by next week. I've gone through 2 drafts, so it's in pretty good shape. I need to add a few sections (screenshots, review, future work, that kind of thing), plus add citations and sources for all the research I've done and tools I've used. I'd also like to add a figure illustrating the security features I've added, and another showing the database schema, plus maybe a few others. I also need to finally finish the UI book I've been reading, so I can write about that. So this is the focus of the current sprint. 

 By way of longer term planning, after that I need to finish the last few development tasks, put together a slide-show for my project presentation, and study for the oral exam I shall have to endure.
Anyhow, here are the sprint backlog items:
PriorityDescriptionPoints
700Add citations for all research done and tools used.2
690Reformat with proper section headings.1
680Add section on rewriting data-access layer if not sufficiently covered and application layer.1
670Add something about UCDetector..5
660Describe work-flow for typical user tasks. (Examples and Screen Shots section)1.5
650Finish Quality Analysis section. 2
640Write Conclusions section.1
630Take screenshots of different parts of app.1
620Create image of database schema diagram.2
610Create image of security layers.1
600Finish reading UI book.3
590Write UI section.1

All this comes in at 17 hours, which is actually not too bad. At this point I pretty much figure my weekends are going to be entirely consumed with the project, so with luck I may even be able to get some other stuff done, too. That would be superb.

Comments

Post a Comment

Popular posts from this blog

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

"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