Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*"
Favorites infavorites:mine
Status closed:yes
Types is:question
Exclude -[tag]
For more details on advanced search visit our help page
Results tagged with Search options answers only user 855

A project is a collaborative and planned activity for attaining a particular goal.

For the specific project there's not much you can do until you find out what the client wants. However, there are some things you can do now so your team is ready to go. How are you going to handle … can have access? Have the group work on a very simple project to test all of this out either in a required language or pick one familiar to the team. …
answered Apr 10 '12 by JeffO
project, but the client pays anyway or now they're able to delay it? Something doesn't add up or the client has a loose interpretation of what urgent means. Both sides seem to be playing a game … , I avoid dealing with clients in this way. A huge discrepancy in project estimates means something is very wrong. Take the project into smaller parts and give estimates for those. This may give the …
answered Nov 19 '13 by JeffO
I worked for a small software company during the time where they released new versions to handle Y2K. To me the biggest differences involve the control and consistency of the users and their environme …
answered May 21 '12 by JeffO
programming. That's the biggest difference. Even if you truly think you can completely write out all of the specifications for a complex project, don't do it if it is going to take a long period of … time. If you talk to a client for weeks on end, go through a lengthy contract negotiation process, build the entire application and return months later with a finished project, don't be surprised when …
answered Jan 15 '15 by JeffO
to delay the entire project? Get them to commit to an increased testing/approval schedule. You may have to repeat the tests on completed areas of the project. As a profession, we need to get over …
answered Nov 20 '10 by JeffO
on a piece of the project and then put together a better estimate if needed. If they keep pushing, you're going to be forced to itemize as much of the tasks as you can an apply a time frame. Tell …
answered Aug 22 '11 by JeffO
Test documentation just like a usability test. Give the document to a user with no explanation and watch over their shoulder to see if they get any value out of it. Hopefully it meets your objective.
answered Apr 7 '11 by JeffO
.). If the project is really small then it's not even in company's VCS. This is the first problem. No such thing as being too small for source control. Get away from email. All parties involved …
answered Aug 8 '13 by JeffO
I would split into 2 teams, each working 2 days. This makes it easier to cover back at the office, have enough time to complete the project and not burden everyone by being away for a week. You also … project, so that may be a benefit. They could just redo everything. Spend the last day with both teams together and debrief/fight it out. …
answered Mar 24 '11 by JeffO
Since your manager knows it will probably fail, you're better off than most. I would consider working with the manager and see if there are any parts/features of the app that can be excluded. Too of …
answered May 10 '13 by JeffO
up any project or application into some reasonable pieces to build and get some feedback before you build another piece? I know this is an over-simplification and doesn't address the actual … hair for 6-12 months while they develop during some waterfall project? Would you hire someone to build a house this way? …
answered Jan 20 '11 by JeffO