“Alone we can do so little; together we can do so much.” – Helen Keller
I thought of writing a post on the collaboration in which we as a team deliver effective products. Despite the hit of the pandemic, we iOS team decided to follow a few tips to achieve our goals through collaboration. There are various types of collaboration techniques available in our digital workplace. We opted for video collaboration to achieve our goals.
The Secret of QUICK DAILY STANDUPS
We could see lots of engineers spending tons of time grooming & developing the product. Scrum and meetings can become effective, only if we follow proper timeboxing techniques. We as a team follow efficient timeboxing techniques by having daily standups.
Daily standups help our team to move faster and together.
It’s All About (The) ONE HOUR RULE
Sitting alone in a room and debugging for more than an hour will make us mad. We introduced a rule like any debugging process must not exceed an hour. If any debugging process exceeds an hour, then it must be communicated to the team for further testing. The idea behind the rule is to avoid procrastinating the process longer and find an immediate fix with the help of others...
CODE AFTER ARCHITECTING: An Incredibly Easy Method That Works For All
Being an ardent fan of Dr. APJ Abdul Kalam sir, we follow his quotes and implement them in our work.
Once the planning is done, we collaborate and design the architecture as the primary process. We shall start coding only on successful completion of architecture. We emphasized this process to create inquisitive thinking that helps to develop a better product.
Modularization: Here Is A Quick Cure For organizing code
“Do not put all your eggs in one basket.”.
It is an idiom that means don't risk everything by committing to one plan or idea. Having all the codes in a single project makes the project heavier and hard to handle. Since it takes 15 mins to build a monolith project, we decided to opt for modularization techniques. This technique helped our team to work independently with less build time. You can find more information on this by clicking here.
Github Branching + Daily Commits + Pull Requests Get the most out of Github
Xcode conflicts are hard to solve with Xcode IDE. Conflicts happen when we work as a team. Follow the below steps to avoid conflicts during product release:
- Branches: It should be created only by their feature context, not by the engineer’s name. It helps to grab the branch context more quickly than asking others.
- Commits: Commit your daily work-related changes before EOD to capture the project’s current changes… There should be no untracked changes.
- Pull Request: Ensure all your changes are merged with the master on a daily basis to notify your team.
Note: RemoteConfig + Bitrise CI on the master confirms the new changes don’t break the old one.
Pair Programing
We love it ❤️. It’s fun and more productive than working alone. People are exhausted working alone in a single room. Doing pair programming improves many factors like communication, problem-solving, and logical thinking, etc.
That’s it for this time! Feel free to comment if you have questions and follow to get notifications about future articles.
“Be the senior engineer you needed as a junior.” — Someone
👏👏👏👏👏👏👏
