Tag Info

New answers tagged

0

This is a difficult problem. You can try to solve this by using feature branching - each new feature is developed in its own branch independently from the other features. You can then have "test" branch where all of these feature branches are merged so that customer can test all features at the same time . When feature A is ready, but B and C are not, you ...


0

As you also said, the efficiency of the team is not likely to get improved if you only have a TEST environment, where all developers work. I think this is the main bottleneck in you development process. Every developer should have his own DEV environment in his local machine, with its own database (perhaps a recent clone from TEST environment). So, each ...


2

Just to rephrase the question. You are blocked on scrum adoption because of the bug in JIRA? That sounds very wrong to me. Scrum is a project management methodology, it cannot depend on tools, tools are meant to be assisting with routine work, not impede it. Hence, my always advice, use physical board, see the progress looking at real tangible things. ...


2

What you apparently failed to do is what any large project needs: project management, documentation, planning, etc. etc. Yes, it's paperwork, it's not fun like coding, but it needs to be done. Make sub projects, modules, split things up according to functionality, define interfaces between those sub projects, document everything, have some diagrams (UML ...


0

There is quite a lot of possible solutions to your problem. You can easily write scripts to automate the steps of the process or use an existing ready-to-use continuous integration solution. I will shortly describe the first solution, where you write scripts to do this yourself. On the server where your webapp mywebapp is deployed, write a small script ...


0

I think what you need is a Continuous Integration (CI) server. You can host your own, for example Jenkins which has BitBucket integration or use a hosted service like CodeShip which has a free plan. You could try and set up your own set of scripts to do a similar job but the industry has already provided a solution in this area. You didn't mention tests ...


3

Although I agree with most of Randall Cook's answer, I would like to add some additional things. Your requirements should be under configuration management and be controlled in some way. That is, you should be able to associate a given set of requirements (perhaps captured in a SRS document or a collection of user stories or a database or some other format) ...


3

Yes and no. Version control is about just that: control of revisions of assets, be they source code text files, images, or even documentation. While software engineers usually put source code and graphical assets (once they receive them) under version control, graphical assets and standards documents are often prepared by non-engineers. In my experience, ...



Top 50 recent answers are included