"I feel that the greatest reward for doing is the opportunity to do more."
Jonas Salk, M.D. ( 1914- 10-28 – 1995- 06-23) - Medical researcher and author.
On receiving Congressional Medal for Distinguished Civilian Achievement (23 April 1956).
Friday, April 30, 2010
Wednesday, April 28, 2010
Managing Stressful moments - Personal organization is key
It is during those moments where you feel more stressed, more overwhelmed by work, by an excess of multitasking or conflict of priorities, that you value more any personal organization methodology.
The simple fact of having a task management system, a recopilation of projects (professional and personal)... will help you handle the stressful moment and succesfully manage the situation.
And if you have to decide dropping or postponing a project, my advice:
Priority 1: What decision will be less painful to OTHERS (or painful to less people).
Priority 2: Never drop the project you are more afraid of. (It's more than probable that if a project challenges your comfort area, that it will finally be the one where you will learn more).
The simple fact of having a task management system, a recopilation of projects (professional and personal)... will help you handle the stressful moment and succesfully manage the situation.
And if you have to decide dropping or postponing a project, my advice:
Priority 1: What decision will be less painful to OTHERS (or painful to less people).
Priority 2: Never drop the project you are more afraid of. (It's more than probable that if a project challenges your comfort area, that it will finally be the one where you will learn more).
Agile or Waterfall - considering scope changes
I received this interesting question on Project Management methodologies:
Question:
"Is Agile better suited than Waterfall for handling continuous scope changes?"
My answer:
Probably yes, Agile is more adapted to change than a classical Waterfall approach. The addition of new features and changes is the essence of the Agile approach: get a prototype as soon as possible and make the product better and better as the needs arise.
One of the arguments against Waterfall is precisely this, although it is not true at all that a waterfall environment in a project would not allow for changes. Have you ever seen a project that had no changes at all during the project cycle? Scope change is also a very important part of any Waterfall approach.
The correct answer for your project will probably be dependent on factors like industry, company culture, type of final deliverable, etc...
Question:
"Is Agile better suited than Waterfall for handling continuous scope changes?"
My answer:
Probably yes, Agile is more adapted to change than a classical Waterfall approach. The addition of new features and changes is the essence of the Agile approach: get a prototype as soon as possible and make the product better and better as the needs arise.
One of the arguments against Waterfall is precisely this, although it is not true at all that a waterfall environment in a project would not allow for changes. Have you ever seen a project that had no changes at all during the project cycle? Scope change is also a very important part of any Waterfall approach.
The correct answer for your project will probably be dependent on factors like industry, company culture, type of final deliverable, etc...
Subscribe to:
Posts (Atom)