Let’s compare two examples, one development environment that uses source control, and one that doesn’t. A: Does Use B: Does not Use Scenario 1: A project is requested, completed, and rolled out A + B) Programmers develop the project internally, when it’s completed, push it out to testing, and then deliver to the client (whoever … Read more
StatSVN does work for Subversion 1.5 and above. See my comment on the SourceForge forums concerning a similar issue reported today on the StatSVN forums.
You might want to think of your story as a vertical slice of the system. A story may (and often will) touch components in all of the architectural layers of the system. You might therefore want to think of your tasks as the work needed to be done on each of the components that your … Read more
To add a ToDo, just comment anywhere in your code starting with the word ToDo //Todo: Get count from database instead To view the list of ToDos, look in the bottom left corner of your Android Studio window: if you open it, you will get this view with the list of your todos and options … Read more
Here’s the fundamental question. When will the client think they’re done? If they think they’ll be done by June, then you put an Agile team in place. That’s 4-6 people for 6 months. That’s the budget. Essentially, you do the multiplication for them. team * rate * 6 months. If they think they’ll be mostly … Read more
I would favour Trac. I’ve used Trac a long time over 7 years by now. I’ve also worked 3 years with Redmine. Latest versions I used in production were: Trac 1.0.1 and Redmine 2.2.3. But Redmine has some serious drawbacks over Trac: Installation is not easy: You cannot use Debian/Ubuntu package system for production use … Read more
And yet, branching should work, and will allow you to maintain two separate versions. If you have a bug which applies to the premium version, fix it on master, and merge it on premium branch. Git will only merge what has changed since you branched between master and premium, ie your bug fix. On another … Read more
Taiga is 100% free and has all the features that comes with something like JIRA. http://taiga.io/ It even has a burn-down chart! So that’s a win! Here’s a site with a nice overview of what Taiga integrates with and real developer opinions on the tool. http://stackshare.io/taiga
Dependencies management is an important aspect of a project’s organization, to my eyes. You exposed in great details various solutions, based on the subrepos feature of Mercurial, and I agree with all the pros/cons that you gave. I think SCMs are not well suited for dependencies management. I prefer having a dedicated tool for that … Read more
On general tips; We are implementing a process of 1) Business Requirements Statement (BRS) 2) Functional Specification 3) Technical specification The BRS covers what the business problems are, and what the requirements are around solutions, testing, security, reliability and delivery. This defines what would make a successful solution. The functional spec details what is needed, … Read more