Level 1 Sprint 1 Planning

-
I figure I may as well start sprinting, as it were, since I've been slowly doing stuff anyway, and this will help me be more organized about it. From my initial backlog I finished two items:
  • Post on Ravelry asking about discrepancies with swatches/question numbers
  • Finish reformatting instructions
It turns out that I discovered a slight error in the instructions (for 3 swatches the wrong questions were listed) during my reformatting of the instructions. So now I can proceed knowing that I have the correct questions figured out for each swatch.

Anyhow those two items are no longer in the product backlog, so I'll proceed with the next-highest priority items. The sprint goal is to finish gathering materials and finish prepping so that I'm ready to start knitting swatches. I think, since this is supposed to be fun and not work, that I shall not have an actual sprint length. It'll just be done when the items are done. The sprint backlog items are:

PriorityDescriptionPoints
900Wind all yarn for project, swatches, and test swatches.5
850Find all books3
800Catalog books in Ravelry and also in a file in the format for the paper2
750Test knit "slingshot" long tail cast-on1
700Test bind off techniques to eliminate having a big stitch below last bound off stitch1
650Test knit a stockinette swatch to find gauge1
600Block test swatch.5
550Measure test swatch.5
500Type up cover letter.5
450Print off cover letter and nice version of instructions and put in binder.5

Which is a total of ten hours. It depends how motivated I'm feeling as to how quickly this will get done. Plus I'm working on other projects (a hat for my dad and a pair of socks) and then there's the fishing that will hopefully happen this weekend, and lots of reading to be done (I still haven't finished rereading the first book in The Lord of the Rings!), so who knows. It's lovely not feeling rushed about this. :)

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