|
The instant some manager or bean counter says the project has funding (this usually happens after you have spent weeks on a prototype).
Timing during the year is totally irrelevant especially if they outsource to s foreign country as they may have a totally different holiday season.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Typically, implementations are planned (by the client) for Christmas, or start of summer holidays, or the week I'm scheduled for a hospital admission, or over the weekend of my wedding anniversary, or any other time when I really don't want to be working. Year after year it happens this way... The joys of being freelance.
|
|
|
|
|
When projects are organized enough to be "started," it is usually June and December. Fiscal year ends at the end of June, and calendar year ends at the end of December, of course. At the beginning of those months, management realizes that stuff must be done BEFORE the end of the "year," and obviously, one month is enough time to get ANYTHING done. Just because people take vacations in June and family gatherings exist in December are not reasons to be concerned that the workforce may not be at maximum efficiency.
|
|
|
|
|
This question is invalid,
there is no season for projects to start
=====================================================
The grass is always greener on the other side of the fence
|
|
|
|
|
For the most part, yes, but some projects have to await funding, such as at the start of the calendar year or fiscal year.
|
|
|
|
|
Was that holiday projects?
Bryian Tan
|
|
|
|
|
Every Month/ or in 2 month.
|
|
|
|
|
Not kidding. Whenever I feel like having something to develop, I work on it. Rest of the months are used to sleep and enjoy the life.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
I've never noticed typical months to start new projects, but I have noticed months when organizations do NOT start new projects.
Those months are July, August and December, which is during summer vacation and Christmas vacation.
Lots of people take those months to plan family trips since the kids aren't in school.
It's kind of hard to start a project when half of those involved are on vacation
|
|
|
|
|
My company is different. We had kick-offs on the 14th of December, with two weeks of break impending I was also to be hired on the 1st of August... with an impending three weeks break.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Sander Rossel wrote: t's kind of hard to start a project when half of those involved are on vacation
On the contrary! That's the BEST time -- you can make all the decisions and get a ton of work done. Less meetings, less arguments, less fools...
Latest Article - Web Frameworks - A Solution Looking for a Problem?
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: you can make all the decisions and get a ton of work done. Less meetings, less arguments, less fools... And then the fools come back and feel left out and you get twice as much meetings, twice as many arguments and all your decisions are recalled if only because everyone who wasn't involved wants to have their say
|
|
|
|
|
The company I am currently contracting with seems to miss vacation planning in their deliberations.
Day one, your a god send, we need to loan you out to this other team. Because you worked in this area before.
Problem 1: I have not seen the code base in about a year.
Problem 2: The resident SME is on vacation for the next month, so you're it.
Problem 3: Everyone on the project, from the PM down, are new contractors without a clue as to how this very complex system works.
Oh! Problem 4: The project was a month behind schedule before they hired the contractors to work on it.
Fun Times
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
John R. Shaw wrote: Oh! Problem 4: The project was a month behind schedule before they hired the contractors to work on it. Brooks's law - Wikipedia[^]
|
|
|
|
|
The Bermuda plan also came into effect.
By the end of the phase 2, my contract was extended.
Why?
Because I was the only one left to complete phase 3.
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
I do not understand that question; how should that work?
"We start a new project every January, no matter, whether the old one is finished?"
This does not sound like planning, but more like pure chaos... either this or I am getting something wrong here.
Development is, in many cases, an ongoing, iterative process, be it scrum or waterfall. in one method you have your sprints, your features and you plan ahead for the next release, in the other there are some crazy stoneage things like kick-offs and months of "designing" and then "development" and then "testing"...
Am I the only one who sees "testing" AFTER "development" to be a guarantee for failure?
IMHO, you should know HOW and WHAT to test, before you write your code... In every other case you stare at 100k line of code and start thinking... "ok how shall we test that?"
I do not say, TDD is the only way to go, but for everything-but-UI it is definitely a way to get easy-to-read, refactorable, TESTABLE and reusable code.
For UI I see many almost-equal methods how to test that.
anyway,... I do not understand that question...
|
|
|
|
|
Exactly. The question was very odd to me, as I never worked anywhere or heard of any shop that started their projects in particular months of the year.
|
|
|
|
|
Some do, particularly if budget is exhausted (start in new budget year) or due to end soon (use up budget before new budget year)
Another reason can be that it's cost means it needs approval from a committee that meets maybe four times a year.
Only worked in that environment once, in a government research place. PITA ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
oh i see...
thank god, my life kept me away from such... instances so far - And now I am too old to enter that world :P
|
|
|
|
|
Mike Barthold wrote: "We start a new project every January, no matter, whether the old one is finished?" Perhaps you should look into work-plans like "agile", and similar Alice-in-Wonderland style Caucus Races. Now I'm not saying you'll actually understand, but you will know it's not beyond the realms of probability.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Well, we are agile for many years now, we know how to plan, we can estimate releases up to six months into the future, but we never say something like what you quoted above.
as i said in my first post, I know well about scrum and agile. and waterfall. glad we left that behind.
|
|
|
|
|
Perhaps you missed this[^] ?
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|