Text entry answers for sorted by frequency of occurrance.
| (2) | CListCtrl |
| (1) | CMFCListCtrl |
| (1) | communicate to the stakeholders about the delays and provide expectations about what will be done and what will be left out and why. |
| (1) | Cut corners and skip documentation. Then come back after release to clean it all up |
| (1) | cut down on the features to be delivered in cooperation with stakeholders |
| (1) | cut down the less important requierements and add them in the maintinance phase |
| (1) | Cut some features |
| (1) | cut the scope |
| (1) | Cut unnecessary features (there usually are some) |
| (1) | Depends on source of deadlined |
| (1) | discuss with the costumer to get a prefered solution |
| (1) | Drink heavily |
| (1) | Drink until i forget about time |
| (1) | Drop Features |
| (1) | Drop low priority features |
| (1) | drop some features |
| (1) | Drop some functionality |
| (1) | Explain to the stakeholders why the deadline will not be met, then stop wasting so much time on Code Project surveys, and get the project finished. |
| (1) | Get stakeholders to commit to minimum feature list with no creep for initial delivery, but architect for at least three expected creeps. |
| (1) | get the quality right before shipping, and also cut features |
| (1) | go to Hawaii |
| (1) | h |
| (1) | Hire Chuck Norris |
| (1) | I have no idea; all the code I have written was open source and without a real schedule (I've yet to code for money) |
| (1) | Ignore small bugs |
| (1) | Ignore subtle bugs. |
| (1) | Implement CListCtrl in the project |
| (1) | Inform the customer |
| (1) | Just laugh in their faces. The fools actually believed it would be done on time. |
| (1) | kill yourself |
| (1) | Leave out some features |
| (1) | Leave out some non-critical features for later |
| (1) | Lose functionality |
| (1) | Manage expectations of share holders |
| (1) | Manage Realistic Expectations |
| (1) | Manage the customer |
| (1) | mattlindberg76@gmail.com |
| (1) | Maybe a little overtime, but nothing heroic. If management makes bad estimates, it's their problem, not mine. Maybe they'll make more realistic estimates next time. |
| (1) | meet with product owner |
| (1) | Missing a deadline is better than delivering a shoddy product that was hurried to completion. |
| (1) | More Shell Dialogs |
| (1) | Motivate team offering extra money / spare time |
| (1) | Negotiate away features |
| (1) | Negotiate features/dates with the client/business |
| (1) | Negotiate for further time or remove certain features for a "phase 2" implementation. |
| (1) | Negotiate functionality |
| (1) | Negotiate lesser scope with a patch after the deadline. |
| (1) | negotiate to omit features |
| (1) | Negotiate with stakeholders |
| (1) | ocr |
| (1) | Only work on tasks for that project |
| (1) | overtime - but keep it within an limit |
| (1) | Panic |
| (1) | panic, cry, fail |
| (1) | Post questions on CP |
| (1) | Pray |
| (1) | Prioritize. Discuss situation with customers. Agree on less-important features than can be delivered at a later date, in order to deliver the main product on time. |
| (1) | Push back some features for next release |
| (1) | Push features to next release |
| (1) | Reduce feature set for the release. |
| (1) | reduce functionality/features + inform customer in-time |
| (1) | Reduce scope of project, then add the missing parts as updates or new versions. |
| (1) | Reduce scope, plan on subsequent release |
| (1) | Reduce the feature set |
| (1) | Reduce the functionality |
| (1) | Reduce the scope |
| (1) | Remove Features |
| (1) | Remove items that are not considered mandatory for launch or causing major problems |
| (1) | Renegotiate contents and deadline |
| (1) | Renegotiate deadline |
| (1) | Renegotiate the deadline |
| (1) | re-negotiate the deadline |
| (1) | re-negotiate the dealine |
| (1) | re-plan and/or strip out requirements |
| (1) | Reschedule the delivery date. Better to absorb the cost and deliver a good product. |
| (1) | rescope |
| (1) | Rethink the requirements and design, then deliver on time |
| (1) | sdf< |
| (1) | Send out resume to usual suspects |
| (1) | shaker sort |
| (1) | Skip nice-to-have features |
| (1) | Talk to the primary sponsor, explain the technical problems and request more time. |
| (1) | There's no such thing as a deadline |
| (1) | Time, Features, Quality - let the busniess decied which one to cut |
| (1) | Work more efficiently and reduce distractions |
| (1) | add more heads and hands to coding |
| (1) | ask forgiveness |
| (1) | Blame the idiot who agreed to the deadline |
| (1) | Break my leg |
| (1) | Caffeine |
| (1) | Change what is delivered (i.e. leave out features). |
Submit an article or tip