Today I was reading the Inc Magazine (August Edition) and there was an article about ROWE, or Results-Only Work Environment, (also known as Results Oriented Work Environment), is a management strategy created by CultureRx and pioneered by Best Buy; the article was really interesting and the point of view of this strategy make think that perhaps is better to use this than be asking to the people to follow their work ours, because most of us know that during those hours we don’t actually work all the time, we all have dead period of time in which we don’t nothing really productive…. So if not good for the company and neither for us.. so why not ROWE?? Will be nice if a company in Peru tries this.
Title: How to write and Illustrate Scientific Papers Language: English Author(s): Bjorn Gustavii Published: 2008 Edition: 2nd
This book will really helpful if you’re writing something, even if this is a thesis project or a Paper, the book explain the concepts very clearly so anyone could read it and apply the concepts, so far is giving me a lot of help for my thesis project. So if you need something read this book.
I think almost everyone knows about the Murphy Laws.. so I wont have to explain all that, the topic of this post is to tell that this Laws really applies… at least for me the last six months of this year have been a fully test that Murphy Laws really happens.
So if your think you have troubles so far… trust me could be worst!!!!!!!!!!!!!!
Title: Thesis Project - A guide for Students in Computer Scienceand Information System Language: English Author(s): Mikael Berndtsson, Jörgen Hansson, Björn Olsson, and Björn Lundell Published: 2008 Edition: 1st
Many people have to do a Thesis Project at the end of the career, to perform this project is need to use and apply all our knowledge about what we study during the years of school, well perform this task could fun and nice or could be really a trouble. For this reason this book is a great start for everyone who wants to do a Thesis Project, the information in the book is really helpful because show us what we must do, how we must, and when. It is basic info but important too. I really recommend reading this book before you even think about to write you Thesis.
Title: Los Templarios y la plabra perdida Language: Spanish Author(s): Mariano Fernandez Urresti Published: 2005 Edition: 5th
This book is not quiet like a History book is more a stories that have some truth from history books. Personally I like History with this book I learn a lot about the templar knights, but almost all the book is full of just assumptions and hypothesis that in fact could be right or wrong. So after that I don’t recommend this book at all. I hope have better luck with the next book.
Title: Agile Project Managment with Scrum Language: English Author(s): Ken Schwaber Published: 2004 Edition: 1st
Most of the people in the project management area use gantt charts and a lot of documentation for the project, also the project the requirements once that have been written, this ones can’t change and if they change they will increase the time and cost of the project in most of the cases.
Other aspect that is normally given for granted is that the communication between the client and the developers must be from time to time what is wrong because this generates basic communication problems that leads to software or functionalities that the client didn’t ask.
The other thing is that with the old fashion methodology the communication in the team of developers is poor with Scrum there is a new way of work that benefits not only for the team, company this change also benefits the software that will be created for the client.
The key thing of Scrum is that the requirements can change from spring to spring this is one thing that the old methodology won’t do very easy.
You'll see how to: •Gain the foundation in Scrum theory—and practice—you need to: •Rein in even the most complex, unwieldy projects •Effectively manage unknown or changing product requirements •Simplify the chain of command with self-managing development teams •Receive clearer specifications—and feedback—from customers •Greatly reduce project planning time and required tools •Build—and release—products in 30-day cycles so clients get deliverables earlier •Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects •Support multiple teams working on a large-scale project from many geographic locations •Maximize ROI!
If you really wan to take project management to a new level you must read this book, the book have a lot of really example of project using scrum some of the are from successful project management using scrum and some of them are from failure when the people use the scrum with out using the correct rules.
Mostly of the software developers don’t like to make schedules. They always said “Will be done when its done” well that’s not correct at all, because a very good pacification is really necessary; of course if your planning to make good software otherwise keep doing with what you are doing.
Of course a schedule must be real, I mean is worthless if you make a schedule and you forgot about it until 3 months after the development is on the way, or if you don’t follow that schedule.
The times on the schedules.. in this point everyone must be really real, even is the client is telling you that everything must be done in a month… If that is not possible.. you must be realistic the day doesn’t have 50 hours, and you cant have 10 people on an small project thinking that less time more people, because that wont work.
Continue with the time of the task on the schedules you must realize that time is money, I don’t want to sound like a person that only cares about money but sadly in the real world companies and corporations only care about money and time, well both are related. The problem is that you don’t schedule your project right, you wont know how long will take, so how do you know how much to charge for the project? Or you will give the client a blind number? What happened if this amount is less than the real one? You loose.
