|
Put it up on git and then /anyone/ add to it. That way you're not the only one getting the ritual thwacks when something goes fubar.
veni bibi saltavi
|
|
|
|
|
Put a price label on each requested feature.
|
|
|
|
|
On a more serious note than my previous reply: Wouldn't it make sense to put a version into production that covers the requirements as per pre-today and then iteratively add the newly requested features?
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
That's basically what i tried to do these last 1,5 years. Problem is, that crucial and really needed functions did suffer under a "You do that now or we don#t see any progress" mentality sometimes. Therefore i can't release a "working" version that would cope with demands on project management. Backgroundworks and Databasestuff were tasks i had to do but no one did recognize it, therefore no "progress".
A lot of +++ work is delayed by me so i can aim for a pre-production version by end of the year but yeah, it's still a lot to got :/
A-SPICE and our processes are some tough enemies.
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Such "Tools" are often ending in a horrible mess. Take a look at Lotus Notes - it can it all... 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
We all know LN is a Dreckstool[^]
SFW
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Quote: Take a look at Lotus Notes
I'd really rather not - I'm still scarred from the last attempt. 
|
|
|
|
|
So, basically you're recreating Outlook and Lync...
How much are those two to implement compared to how much you get paid in the next two years? Chances are really really good that YOU are the more expensive option.
|
|
|
|
|
Not 100% correct, the system i am developing is not available on the market as it is espacially designed for Automotive SPICE Projects and + for common project management. The additional features that are requested do not fit in any software that exists (AFAIK).
It's a complex structure that combines Projectmanagement with Projectflows controlled by tasks but measured by "Workproducts" with integrated Riskmanagement and Resourcemanagement + Projecttimes.
Also a Link to a DMS is required to control the "Workproducts" on a Versionbased Level.
If you know a Software that can handle such things let me know!
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
HobbyProggy wrote: The additional features that are requested do not fit in any software that exists is available on the market
FTFY 
HobbyProggy wrote: If you know a Software that can handle such things let me know!
Yes, but this specific one isn't for sale.
|
|
|
|
|
Jörgen Andersson wrote: Yes, but this specific one isn't for sale.
You see why i got to dat by hand ?
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Indeed, and 1.5 man years sounds like quite an underestimation to me. Demand a feature freeze, so that you can concentrate on the core functionality.
|
|
|
|
|
HobbyProggy wrote: a complete workspace for everyone with integrated messenger and notification system. Displaying all Vacation, Meetings, Tasks in a fully customizable Shedule
Just tell them to use Google. What else do you need? Calendar, messaging, phone notifications of events...
Marc
|
|
|
|
|
Launch what you have and do bi-weekly sprint meetings. So launch on day 1 and decide on what feature/features to release in two weeks. Then sprint toward those and only those features, leaving your yourself some time to fix bugs and then do it all over again.
Some weeks might not have "features" but might be bug fix weeks. The important thing is that Management, with your input, decides what features are delivered each sprint. If a feature will take multiple sprints that break the feature up into smaller parts.
This helps to avoid the software death march: http://en.wikipedia.org/wiki/Death_march_%28project_management%29[^]
My two cents.
Eric
|
|
|
|
|
First, please admit that you chose a dangerous path. When it comes to buying software vs. writing software, always buy! Unless that is the product you are going to be selling to others.
Second, this is nothing more than feature creep. In managing projects, the most important task is to manage expectations. In order to do this, features have to be labelled as such, and requirements labelled as such. This new calendar piece sounds like a feature and not a requirement. Write it up, push it aside, and move on. Having these ideas are great. Derailing a project for them is not.
At this point, I would reconsider the buy vs. write. Any significant change in the production cost requires reviewing past assumptions about buy vs. write. Review products again that exist and are close to what you need. They may be a lot closer now. The other thing that happens here, is you realize there may be a simpler way to accomplish what you are trying for if you push ahead.
Finally, be agile enough to get a working product in peoples hands as early as possible. This will help you focus on the value proposition (what can I do today that eases the most pain for the users).
Good Luck
|
|
|
|
|
It is simple.
Add every feature they requested to your Story board. Cost the new stories in both time (remember everything always takes longer than you think) and money. Make sure stories have prerequisite stories.
Have a meeting where you display the additional time and the additional money it will all cost. Just be honest.
Example: X feature requires a custom calendar control, two-three weeks . . . just for the Calendar control. Hooking up the calendar control is a different feature. Of course, the Calendar is a prerequisite story to hooking it up.
Then they have the stories, and the time each will take. Let them worry about which ones to play first.
|
|
|
|
|
Big ideas are large in scope and devoid of details. Then everyone has an idea that would make the project so much better. The reality being they just want credit for showing up. Most of the people who have these wonderful ideas have no tech skills thus you have to figure out how to make the damned unlikely (read impossible) work.
"I opened your web app and it doesn't look good on the 600 X 800 resolution."
|
|
|
|
|
Tell them that they have to come up with the charge number. That always puts a huge break on people asking for features in tools.
|
|
|
|
|
And pint is measured in Imperial or US?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Never share your pint with anyone!
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
A share pint (two words) would be a very small share in a brewery.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Do you realize that you have more than likely brought Nagy out in cold sweats at the thought of sharing his drinks with others.
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
I'm not sure Nagy familiar with the pint (hint: it is too small for him)...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
