Project Evaluation and Management
--Originally published at TI2011 – Press enter to continue…
It sounds like a diet, or maybe some kind of weird and aggressive technique to lose weight. I read this term in the Deadline Novel, and I was like, "what are they talking about?" "Organic Well Lean Noodles..." by coutaskdwfv https://flickr.com/photos/185642019@N06/49106899981 is licensed under CC CC0 In the novel, they satanize this term, for a … Continue reading Lean and Mean?
--Originally published at TI2011 – Press enter to continue…
"Staff Meeting" by ljguitar https://flickr.com/photos/ljguitar/7697808370 is licensed under CC BY If you've ever worked in any kind of software project, you've experienced meetings. Depending on the size of the project or the place you've worked in, you may have experienced the useless meetings that are only consuming programming time. In college, I usually have some … Continue reading Reminder alert: Another meeting in 5 minutes
--Originally published at TI2011 – Press enter to continue…
Over the past few posts, I've written about what project managers usually do that may cause the project to be finished even later than was expected. Today I bring to you: Overstaffing "All Dressed Up :)" by Thru My Shutter https://flickr.com/photos/185261736@N07/49141762121 is licensed under CC BY-NC-ND If you're a manager, the project you're managing is … Continue reading Another way to not reach the deadline
--Originally published at TI2011 – Press enter to continue…
It feels like it has been a lot since my last face to face interaction with anyone. Yeah, it feels like this This semester started like every other semester, but there was this news about a new virus spreading out from China. On those days, there were really few people who thought life would be … Continue reading Learning in times of a pandemic
--Originally published at TI2011 – Luis Wilson
Here we are again, just a couple of hours after my last deadline post. I like these ‘exams’ because I don’t really need to read. I mean, I could read about things I want to write about, I suppose.
It’s been a wild ride. This year is actively trying to kill us and we must keep on schooling and working. I’m not saying it’s the wrong thing to do, we have to keep going while scientists or whatever figure this one out. We can’t do anything else besides staying home and trying to be productive but, jeez, it sucks being stuck in the same chair for hours on end doing homework and/or working.
While I have not completely lost sanity due to being inside my house all the time, school and work definitely have made me lose it. I’ve cried, not slept, procrastinated and all that Gen-Z stuff you hear about online these days. Still, I did very well regarding grades, but I do see where the sacrifices were made.
I do feel stronger, and more resilient. Not saying that it was the healthiest thing. It is what it is, and I have to adjust. Everyday I try to be better: exercise a little bit, get more rest, stress less, ask for more help. I’m not getting ‘cured’ anytime soon, but I can see progress almost everyday. Of course, some days are just not great and hope that the next one is better.
Well, we had many resources:
The book is just so real with the themes it handles. Not the actual story itself, but its ‘academic material’. I can remember a couple of times I was reading a chapter and being all
--Originally published at TI2011 – Miguel’s Blog
This is the final reflection for the course. This will first cover the topics that the last third of the book covered and then I’m talking about what I learned from the book as a whole. One of the first topics covered in the last part of the book is that some projects often skip the design process. Well, design will be done, but when implementation comes around, the programmers will just not look at the design and design as they code, which can lead to a high number of bugs. It’s also discussed that sometimes it’s better to just do design for a long time, try to get the best design possible and that design should be easily transferable to code. Then you can do last minute implementation and end up with few to no bugs. The problem with this in the context of the book is that the teams were overstaffed and design is a process which will not be sped up by adding more people, it might even slow down. When coding, more people can often reduce time. A dynamic team size throughout the project’s lifespan is the best way of doing it. Personally I think this is true, design is difficult to do with a lot of people, you have to communicate with many others when doing something that the time that you actually spend doing design decreases.
Another topic that is covered by the book is the size of meetings and the way meetings should be carried out. A meeting agenda must be defined beforehand. Not all meetings are relevant for all people, so having someone in a meeting that serves no purpose to them is only wasting their time. It’s also mentioned that there are some steps to take when starting a meeting. This
--Originally published at TI2011 – Luis Wilson
Well, this is the last chapter of the book. I still remember all the chapters like I read them yesterday (basically).
Talk about rushed endings. Though, I always felt some chemistry between Lahksa and Webster. I mean, who wouldn’t fall in love with their abductor? This is some Stockholm Syndrome type of stuff.
Despite the story being ‘just okay’ I think I got its point. The story is just a way of teaching a lesson, in this case, about management in software. I did learn and relate to tons of stuff. If they had layed out the topics like a highschool textbook, I probably wouldn’t be alive and writing about this right now. So, good for you, The Deadline!
While this chapter was a filler to end the story, we did see something referencing the last chapter which I didn’t cover in its respective blog post.
This is shown as Tompkins’ last entry (journal entry):
When he mentioned it last chapter, I realized I didn’t get it but brushed it off. I mean, goals and estimates do mean different things, that’s for sure.
The questions come from the last statement, where it says they SHOULD be different. It could make sense (speaking through my mind’s perspective): an estimate could be the objective and real calculation while the goal is the dreamy date that motivates you and you hope is finished by that date. But just HOW different can they be?
The way I see it. Your estimate is your hard deadline (hopefully it doesn’t get pushed back, but it can, everything’s possible). Your goal should be aimed at an earlier date, don’t know the details, but it shouldn’t be an exorbitant Continue reading "The End: The Deadline Chapter 23"
--Originally published at TI2011 – FABIAN'S GEEK STUFF
It is funny how some radical event like the one we are living can make us change us all. I was just reading that many people or activist are doing massive events online and more specific live streaming. But sometimes they just like to get their thoughts out and say whatever they thing because, what... Continue Reading →
--Originally published at TI2011 – FABIAN'S GEEK STUFF
This is your well known section I'll talk about everything that have made impact to me. And yes it has been an instes las few weeks. The projects and exams do not stop. Make me realize that hard work can be pay off. I encounter myself to 2 exams left, with no projects and many... Continue Reading →
--Originally published at TI2011 – FABIAN'S GEEK STUFF
We finally have ended this long path, a section must be close and this is it. It was fun while it last. I will make sure to write more content like this or at least keep posting lik I have. A vision is placed to Webster and as have previously watched he have done a... Continue Reading →
