Surviving at the Software Industry. (4)

Today I'm gonna try something different. When I write about something I usually have all the resources on hand. But I feel my two last blog entries have been pretty stiff, so today I'm going to do it just by remembering the chapter, so if I'm missing something important, please tell me in the comments below!

I found this guide is just that. A guide. I'm learning as if a friend was telling me how to do something and not as a regular book, and that's just lovely. Now I know what book would I take with me if I was on a desert island. (Guide on building boats.)

 

So this chapter talks about those skills we should have if we are planning on starting a project.

• Checkpoint Overview: Having mock-ups and UX prototypes, and stuff like really well detailed software requirements is super important when you are about to take a decision on doing a project or not.
• Risk Management: Being prepared for everything, even the worst-most-impossible scenario out of all. Failure in some cases could mean the team not eating for a while, and man, humans literally can't work that way.
• Project Control: Everyone is doing it's part and CAN manage it. As a project manager you are responsible for the life of your project, as well as the well-being of everyone on your team.
• Project visibility: Have you ever felt that you "kind of" achieve something while coding? Visibility helps you to understand what have you actually done and what you haven't. It is important for a PM to know in what ACTUAL stage the project is at any time.
• Peopleware: Rule #89 of being a programmer: Never forget that normal people don't know how to code. Knowing the people that are going to use the final software is as important as the code developped.
• User Involvement: We may think we know what people want on a software app, but we don't lose anything on asking. Talking with others can give you a better idea on what is the actual things you would want to see in a project.
• Product minimalism: Man, I just love minimalism. It makes everything so simple and neat. Just as your code should be! If it is simple and readable, you can detect errors faster!
• Focus on shipping software: Everyone must know they are developping the same thing. I know this sounds stupid, but if not everyone is on the same page, a project can't go right.

PD: I did cheat a little by copying the names of the titles, I'm sorry I don't have a perfect memory don't be all like this. See you soon, bye.