Sprint 3 Retrospective

-
Sprint 3 is now complete. It went fairly well, although again I had trouble finding time to work on the project. There were some other frustrations which I'll detail below. I finished 3 backlog items: Run automated tools e.g. FindBugs to ensure code is correct and clean (8 hours), Write a shell script or similar to start the database server and tomcat (1 hour), and Fix the build.xml to only copy the correct jars to the web app's lib directory (15 minutes). Then there was the stuff I worked on a lot and didn't get done...

I started on both Restrict the login page to only allow access via SSL and Fix the email notification system so that it works with the CS department email settings. For the former, I got SSL redirection working if the user navigates directly to the login page (e.g. http://localhost:8080/ProjectManagementSystem/login.html) but despite my best efforts I couldn't figure out how to get it to redirect if the user goes to the root of the web app (http://localhost:8080/ProjectManagementSystem). I posted on StackOverflow days ago and still haven't gotten any comments or answers, so I'm not sure what to do at this point.

For the latter, I did discover what the trouble is with sending email alerts using the CS department's email system. Unfortunately I really need to consult with my professor before I can resolve this, and since I didn't get to it until this weekend I decided to wait until I see him tomorrow to discuss it; I doubt he'd be checking email this weekend. Basically authorization is required to send email, but since the department uses a self-signed certificate, Java doesn't recognize it and throws an error. The most correct way to remedy this would be to add the certificate to Java's trust store, but that requires admin access which I obviously don't have. So I need to find out if I should implement the workaround of temporarily storing the certificate (which will take a lot more effort) or accepting all certificates (not good for obvious reasons) or if the prof would like to add the certificate to the trust store on the machine where he'll be running my project or something else altogether.

The only backlog item I didn't work on at all was Move properties out of the session so that users can do things like have multiple browser windows open and bookmark pages, which I probably need to re-estimate; upon further reflection this will require rewriting the entire database access class (which it does desperately need) and that will probably take more than just 8 hours.

I'm not going to do sprint planning tonight, as I need to discuss these issues with my professor and prioritize in general for the next sprint.

Here's my burndown chart (subtract 10 off all numbers on the y axis; I wasn't paying attention when I drew that...):


I'm really hoping I can work on the project more evenly for the next two weeks so I can get more work done. Here's hoping...

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