Best workflow for a web development team to work on a large amount of projects simultaneously? [duplicate]

softwareengineering.stackexchange https://softwareengineering.stackexchange.com/questions/283077

  •  08-10-2020
  •  | 
  •  

Question

We're a team of web developers, and as the number of projects we're working on has grown and continues to, things are starting to get messy.

What we currently do is work on a locally shared folder and sync files to production FTP hosts on save.

It's far from being perfect, but we have yet to find a better solution.

These are the main things we want to achieve when changing our workflow:

  • Fast reading and writing to files
  • Fast testing on the browser after saving
  • GIT

Frankly, we're not very experienced with more advanced workflow

Most of the team doesn't know how to work with Git at all and would rather stay with their current workflow, therefore we're looking for a way to achieve the points above with as few changes as possible

Was it helpful?

Solution

  • You need to have some kind of version control system. You MUST have it. If git looks too complex try mercurial, even thought they are very similar. Set up a git repository server. My team uses gitlab and it works fine.
  • You need to put some rules for the control versioning. Meaning, ideally not all cannot commit to the main branch for example.
  • You should start to do some testing. Maybe unit testing is too difficult to implement right away, but you should do some testing before making a commit for a branch. I mean, it should at least compile and run right? Well, sometimes people make commits that doesn't even compile. You HAVE to do some testing if your team is growing. You don't say what are you guys doing or what language(s) you are using so I cannot give you any specific help, but maybe you should take a look at Jenkins.
  • You should use some kind of bug reporting tool. Take a look at these: http://mashable.com/2014/02/16/bug-tracking-apps I've used FogBugz and I like it. I heard you can now use it with trello.
  • You should use some kind of tool to communicate with your team and share ideas, like trello or something like that.
  • Try to have an homogeneous environment. Meaning, if different persons use different OS and compilers, things can get messy.

OTHER TIPS

The hardest part about having a lot of projects and a lot of people often isn't about how to maintain the code, it's how to communicate, implement the process, and work together with good tools.

To achieve that goal I'd recommend you

  • use git for source control
  • use jira, trello or privotal tracker for issue tracking
  • use agile processes and look into using kanban to focus on the work.
  • use slack for communication (it has recently swept thru the industry).
  • use remote repositories such as github or stash to store code.
  • use a full-time scrummaster for process
  • arrange team(s) that have developers, a scrum master, a Product owner and QA for process
Licensed under: CC-BY-SA with attribution
scroll top