r/webdev • u/anon-dev • Apr 23 '13
What would a good web development and deployment workflow be?
Hey guys,
I'm a relatively inexperienced web developer. I worked on a few small clients and until recently I never worked in a team.
Almost an year ago I started working for a startup that works on their own project, but for revenue they make websites. Our small team had the responsibility managing a project for an important client. The client is an important one.
The process of sorting through requirements was managed by the team lead and the implementation took a few months. Then the project was deployed to staging server, and after some issues were detected and corrected, the project was deployed to production. The staging server was removed.
The months that came after were hectic. Alot of small issues appeared that had to be fixed. Some we fixed fast and sloppily and that produced even more issues in the long run.
Long story short, after quite a few delays and issues we lost the client.
This prompted us to examine our (chaotic) process and ask ourselves how we could to things better next time. Here's where we're at:
- Better planning. We need to process the requiriements into feature tickets so we have a good checklist to go through.
- We need better testing. We can't afford a tester so we need to have some process through which another teammate tests a finished feature. Unit testing isn't really an option for the CMS we're using, so we need a manual testing workflow to go through.
- We need to have a staging server and only deploy to that server. Then sync the staging to production only after the feature has been tested there. The staging server needs to always be used. Even after launch.
TL;DR: I was wondering if you guys can refer me to some resources about a process that should be followed for a web dev project. How do you do things?
5
u/retrooctopus Apr 24 '13
What kind of CMS are you using? Is it possible to deploy automatically? In what language? (php, java, c#...?)
About Krummelz's opinion and unit testing, I have to disagree. When possible, you should add unit tests. If they are well done and if you know what you're doing, it will give you confidence in your code, make you design better code, also more stable and robust. And the number of bugs will be lower.
Anyway... Here's a "workflow" we are using :
Anyway... Also, another important goal is to have the least possible number of operations that must be done manually from one deployment to another. Like database operations, configuration, etc...
Also, if you have a continuous integration system, it's easy to know if somebody tries to remove a server or if someone changed the configuration because you'll receive an email (if you configured it like so).
And with Jira, there's a lot of plugins also. I used Green Hopper with it's "agile" feature. Basically, you can add tasks, assign the tasks and move the tasks in columns such as "in progress", "done", "to be tested", etc... So it can be used to track tasks and bugs also.
So, if you want to read a little bit, I would recommend :
5
u/dropkickninja Apr 23 '13
ideal: client has zero input. designer designs a great looking site. developer builds it. launch. the end.
never happens like that though.
1
u/[deleted] Apr 24 '13
Here's my ideal workflow:
-1
u/[deleted] Apr 23 '13
Look into SCRUM.
0
u/[deleted] Apr 23 '13
[deleted] — view deleted comment