Software development can be very finicky and the team that makes can be even more so.
It’s counterintuitive, I know. There’s a temptation for managers to add more people to a development effort to speed things along. The maxim that modern programmers and teams are aware of is that adding more people to the project will frequently delay the project.
This doesn’t necessarily apply to agile methods. That said, frequent and large changes can break a project. Sudden changes in scope can make an awkward case for the team. If the stakeholder makes a request, try to let them down easy.
You will not be able to catch every single bug. By all means, you need to try to make the best product you can. However, if you’re making software for a profit and you’re not flying big metal objects in the sky, sleep well at night.
Spending hours formatting pixel-perfect images may not be the best use of your designer. Figure out what’s important.
Don’t save time by letting your developers write crappy code. It will have to be redone and frequently at a higher cost.
Technology cannot solve a management problem.Read More >
Need to find out who has been on your Service Now instance but got two or more nodes? Use the following method to get ahead.Read More >
Unilateral decision making is dead. If you've recently been placed in charge of a team, you might be acquainted with something that you've not had before: authority. Don't let this new found power put you in the precarious position of thinking that you are better than those under you. You may be a superior, but you're not superior.Read More >