2 ms·
It's not "agile" but very much suited to your situation, MVC, as a developer you would maintain the Model and Controllers. The UX/UI designer sticks to the Vie
by xd 16y ago
It's not "agile" but very much suited to your situation, MVC, as a developer you would maintain the Model and Controllers. The UX/UI designer sticks to the Views. Apply agile methods around this. As to which, you will need to experiment and see what works for you.
And take the time to learn each others skill sets and talk about the reasons why you do things the way you do. Most of all challenge each other on a daily basis.
Oh, and have fun.
- haploid 16y agoThis. Hopefully you've selected a component or mvc web framework that enables clear separation of roles, to minimize integration bottlenecks. As for processes, Scrum methodologies such as the daily stand up meeting and weekly defined iterations would probably be beneficial. But take that with a grain of salt, since some teams simply don't work well with such fixed parameters. Give it a try, but don't stick to it out of obligation. Stick to it if it works.