Search Results

I'm sure there are some difference between the development of a framework or library and an application. Development processes are essentially the same. The differences may come down to marketin …

On the contrary, it sounds to me like an Agile method is exactly what you need in order to deal with missed deadlines, unrealistic expectations, and poorly planned projects. Your management have indi …

Software development is a skill that is learned through study and practice. I would suggest you stop and have a think about what it is you want to achieve before you even begin to do more than sketch …

The possibility of project failure is something that you try to factor in early on. If you see a project has a very high probability of failure, either it won't get off the ground, or in the early ex …

It really depends on how your hardware team will deliver useful artifacts that your software team can use to develop against, and how the teams are set up to communicate with each other. Typically, y …

Off the top of my head, here a just a few reasons why it is important to keep a log. If you wish to patent something you have invented, then a log book becomes a very vital piece of evidence. If you …

Take a hands on approach. Start by grabbing yourself a simple C# primer and write some code. Try a few basic things that you would know how to do blindfolded in another language. Read up on programm …

Speaking from an Agile perspective, you generally want to create tickets describing stories/features that take you between 1-3 average weeks to complete. This of course may vary from methodology to m …

I don't have access to hard data or facts, so I can only offer you anecdotal observations gleaned from my last 20 years in IT. I believe there is a vast difference between the that way most developer …

You have a couple of ways you can go about this sort of thing. If you spot a problem in something you have worked on before, you could: Fix the problem as a part of the task you are working on - re …

Issue tracking isn't project management, even though many of the tools are designed to allow you to do both, so therefore one system doesn't really replace the other, A Kanban board gives you a love …

You want to start by doing some sort of a cost-benefit analysis. You aren't truly going to understand how important it is to simply start over without being able to prove that this is the best approac …

Refactoring is - and should be - an ongoing process. It's not enough to simply meet requirements with a working and tested implementation that is still a little incomplete. "Make it work, then mak …

Managing bug resolution really needs to be handled on a case by case basis, and scheduled according to both business needs and the nature of the bug itself. With that said, if you identify a bug whil …

Getting an entire team to all actually want the same thing can be quite difficult. It's often the case that seeing the value in something isn't enough in itself to encourage people to change ingrained …