Acism is the pioneer in the new age model of crowdsourcing software development. This model is better suited to the “new normal” post Corona pandemic, than the traditional way of doing software development. Acism nurtures a community where the community members collaborate on software development remotely. Most of our outsourced software development activity uses this model.
- Remote working was forced during the pandemic. While it was initially carried out as a compulsion, soon people actually started seeing many benefits of that. The remote working is here to stay. A significant percentage of workers do not want to go back to the routine of going to office everyday. Some companies have disposed off their real estate.
- The shake-up of industry made several productive workers lose jobs and they have become available for work. Most productive people are not the job-hopping types, and hence it is rare that they are available at such a wide scale. Therefore, this is the best time to build something that requires the best of people.
- Unusual times call for unusual measures! The pandemic has forced people out of their comfort zones, to consider newer ways of doing things.
- Xsemble technology makes it possible to break a software development project into small disjoint activities at individual level, without needing a co-located team. Xsemble aids the management through giving a quantitative progress of development work in terms of components.
Enhanced Software Development Process
The enhanced software development process is captured in the following process flow diagram (courtesy: 10Xofy whitepaper). As one can see, it has some activities borrowed from the conventional process, and some other activities that are related to Xsemble. The latter ones replace those parts of the conventional process that require dealing with a large code-base and the lack of visibility associated with the difficulty of the same.
The community is an engine to execute this process to deliver software projects reliably. The Project Manager (PM) designated to the project chooses the team and assumes overall responsibility of the project. An activity gets unblocked when its inputs are available. The Individual Contributors (ICs) work on the activities, starting with the inputs to the activities and delivering the outputs. The PM schedules the activities, tracks progress and has the end responsibility of accepting / not accepting the delivered output.
In some cases, the client may themselves want to retain certain activities to themselves. For instance, they may already have a UI designer on board, or they may want to keep the testing part to themselves. Such permutations and combinations are usually possible. This is explained further in our buffet menu blog post.
Benefits to Projects
- The projects have an huge pool of manpower to tap into, limited only by the availability of the community members. The choice lets you optimize in terms of skill and expertise on one side, and cost on the other.
- A programmer can become productive is no time, as the need to understand a gigantic codebase is absent. It is therefore easy to get more programmers onboard to deliver critical timelines.
- The enhanced software development process brings unprecedented transparency to software development. It is useful for tracking and course-corrections.
- The projects get executed at optimum cost. One does not get paid for rejected work. Contrast this with team members in traditional project teams who are billed to the project although their deliveries may not be good. Further impact on cost savings due to the use of Xsemble technology is covered in Xsemble’s introductory slide deck found on xsemble.com.
- There is an built-in fault-tolerance and resilience in this model. When someone does not deliver up to the expectations, their work gets rejected. They may be given a chance to improve it and re-submit, or the work may get assigned to someone else. This makes sure that individual lack of skills or professionalism will affect the work least, and a reliable output will come out.
- Your IPR can be protected much better when individuals located across different geographies work on parts of the project.
- Your software is highly enhanceable and maintainable for life, as it is made up of tiny components. A change can be planned visually with the help of the Xsemble flow diagram to affect certain components or needing new components, and then programmers will need to work only on those components. Again, it does not matter if these are completely new programmers, because the learning curve for a tiny component is negligible.