When utilising existing systems and platforms we consider 3 options:
- Availability – is the solution available to all members who require it
- Suitability – does the solution cover every feature that is required
- Licencing – is there an ongoing licence involved that effectively forces the decision
This approach is useful when finding solutions to bring teams together and optimise the delivery of a project.
Some examples of where this approach has been applied include:
Using software that supports inline code formatting and group collaboration is vital when working in a highly-functioning team.
Whether a team consists of 1 or 100 members, being able to manage versions and revisions is essential with fast-paced delivery
To deliver a product in a modern, agile manner, being able to test inline and deploy automatically is the difference between error-free code and unhappy customers.
Another crucial part of the decision-making process when it comes to instant messaging is bots. Historically, notifications from messaging services are associated to other team members, but it is widely accepted that other notifications such as deployment notifications (success and failures), code Pull Requests and automation test results should come through to the main location that team members collaborate. Too much noise in these places can have a negative impact but having crucial information in a centralised place for all to see results in faster responses when an issue arises.