Collaboration Tools and Methods in Software DevelopmentPAUL RUSCIOR

STEFAN FODOR

VLAD ZAHAN

6 T H M A RC H 2 0 1 3 PSS

Overview• Introduction / Why we needed this

• What we’ve done so far

• What we want to do in the future

• Question

Introduction• Working together for 3 years

• Reached a certain level of efficiency

• Work on various non-school related projects

• Need for• Developing more in less time• Time is money

• Maximize efficiency • Remove the time wasters and zero-productivity periods

The time wasters• “Hey, can I have your updated part?”, “Here is my updated code for the backengines”, “Do you

still got that old version where …. ?”• Missing files, incompatibilities, accidental rollover to older versions

• “What should I do next?”

• “What is this fooBar() function doing?”• Especially after partial code merging

• “This part that you wrote is not working correctly when ….”• Forget about the bug

• “OK.. Let’s merge the code”• Things will break, will not fit, good code overwritten by dummy functions, split functionalities

Git and Bitbucket

Git and Bitbucket• Things we can handle• Commits/push• Pull, clone• Rollbacks• Basic branching• Tagging

• Still need to learn:• Advanced branching• Conflict resolution• Proper merging

Task Tracker

The future• Finish with Git

• UML

• Proper code documentation standards

• Conflict resolution tools

• Bug tracking tools

Thank you!

Collaboration Tools and Methods in Software Development

Questions?