Thanks to the cooperation of business with IT, software development can be very easy and pleasant.

Every day, managers expect something from the IT teams or people from different teams, in most cases, these teams do not work in one place, in one branch, they are dispersed in different locations. Thanks to the KanBo board, they can transfer their needs in a simple, easy, fast and intuitive way. It also works the other way, people from the IT department can quickly ask in the context of a given topic, what exactly are the expectations for a given task. At any moment, they can present a dedicated solution and show what they have worked out to make sure that everything is going in the right direction and that something needs to be improved.

 

What is software development?


The software development is a process consisting not only of writing code of a software but also of specifying, testing, fixing, maintaining components of the application of service.  The process might also include the following actions like researching for best solutions, controlling, re-engineering and prototyping software. This set of actions make the entire process very complex and they must be performed by a staff consisting of highly-qualified members. Such collaboration is necessary between IT teams and Business users (such as managers) to achieve acceptance and lead to fulfilling of the common goal.

 

5 principles of efficient work on software development.

1. Communication between IT and Business users is crucial and necessary to achieve common acceptance together regarding software’s shape.
2. A platform for communication and sharing feedback regarding software is required so there’s no need to organize daily, time-consuming meetings to discuss current matters.
3. Ability to work from everywhere and from every accessible device is important to maintain the good performance of every party.
4. Developers require clear instructions what should be developed, and what should be the shape of it. There is a need to have instant access to the most recent materials and documents such as specifications.
5. Developing a software should have a clear and transparent process of approvals, testing and flow.

Are you interested in how these values can be tied together and improve your company’s workload?


See the Software development process in action!

We have prepared an exemplary Board to show you how easily you can manage process of software development, using KanBo. The Software development board represents a complex project of creating a new IT product in which employees from various departments and areas are participating.

To see it live, simply request Sandbox trial here for free, log in using the provided credentials and check out our Software Development board.

Here is the description of all components of such project.


Ability to work on a common goal between various specialists

The Software development team consists of specialists in various areas: developers, testers, Q&A engineers, R&D team members, team leaders, and managers. Such team is capable of performing the entire process of creating software development in any of its forms. As R&D team members are capable to prototyping the software’s shape and developers are specialist in the field of coding it, there is also a need to test the software by professional testers and approve all actions by managers.

In KanBo it is easy to figure out who is responsible for which matters in a project or process. While entering User Profile of any team member, it is clearly visible what is the user’s role in an organization and how a person can work with others to achieve a board’s goal.


Board – the process of developing a software.

Getting the right place to perform the entire process successfully is surely a crucial matter for the organization. KanBo Board ensures that all communication, collaboration, and processes are collected together. What’s more, they can be re-used later to perform processes to come in the future.

To indicate the flow of creating software, there are 7 steps, matched with right descriptions of their purpose:

Planned features – This is a list of planned features that we are thinking to implement. We’re still in the planning phase which means that we may or may not get to add the feature, but we’re looking into. Once we decide to work on it, you’ll find a new card in the ‘To do’ list to the right.

To do – A list of tasks which are approved for creation are collected there. When we start to work on them, move any feature and component to the next phase.

Doing – Here are cards which goals are currently being developed. Feel free to discuss the final shape of features in these cards. Once the code is created, reviewed, submitted and the features are implemented to the build, move them to Done.

In test – Features, and components which await testing by testers and Q&A specialists. Once tested, they should be moved to the next phase.

Tested – Approved, implemented in a build and ready for final deployment.

In approval – Here cards are waiting to be approved by management and team leaders of this project. Move them to Doing if they do not meet requirements and these cards will go through the change process. Move them to Live if the cards meet acceptance.

Live – Features and components which are accepted by management and moved to the production-ready package.

It’s very easy to see the purpose and role of each list as the description will pop-up once a cursor hovers over the list.

 

 

Get more insights into the shape of a project

Management and team leaders of the software development project would like to get real-time insights of the progress in this board. This is where Gantt charts and Analytics come to place.

Gantt charts provide a comprehensive view of flow and progress in a project. What’s more, every person can not only see details of how much time is left to finish particular tasks but also can see details regarding relations between various cards.



If there is a need to see what is happening inside the Board, the Workplace Analytics component can be used. Thanks to this feature, users are presented insights about: the most active users, the progress of cards, how many days left until the card is finished, how many cards are finished, how many are late and how many have not even started.


Context – the center of work collaboration

As soon as the workflow is planned by using lists, tasks should be assigned to the software development team. We have created cards indicating features or components of the software to be created.

Let’s talk about the important elements of the cards which we have used for this case.

  1. Card members should be assigned to a card so everyone would know what’s their role in a job or tasks. In the provided example, users from different departments are assigned and are discussing the share of a component. The person responsible is a user which takes the care of a functionality and other co-workers can discuss and provide any needed materials for a responsible team member.
  2. Notes in a can might be helpful to describe the goal or specification of any component in a short manner.
  3. If a specification might be changed frequently or is quite big, any document can be added to a Card. KanBo supports Document versioning and thanks to it, all changes of the document are indicated in the card’s stream with information who was the editor.
  4. ToDo lists might help the team to enumerate sub-tasks or functionality’s sub-components. It’s very easy to check them as complete or uncheck them if any change appears. Also, it is known that it’s simpler to work on sub-tasks by breaking one huge task into many smaller ones.
  5. The stream of the card is a special place in a card where activities are indicated. It is a place for discussion, giving feedback or advice to other team members. Card’s stream also tells us what are the actions which happened in this card which makes it a „log” in the card’s terms. It’s possible to switch between „detail levels” of stream’s activities and that allows you to see only what’s the most relevant.
  6. Adding card dates to a card is also essential as this functionality helps to estimate a time frame of i.e.: preparing the code for functionality, assign a date of final deployment etc.
  7. Labels are a crucial part of the card as they give an additional description to a task, i.e. about its importance, approval process, version to which functionality belongs to. Labels can be used by management to perform the approval process. In our case, once a feature is approved, it can be deployed into the final build of the software. If not, it should return to previous Doing lists, so the change requests or improvements might be performed by developers.
  8. Subcards give you a possibility to maintain relations with other cards when a single card is not enough to plan work on one component.

Use these elements also on your boards to make your workflow even more efficient!


Try it yourself!

We have provided you a real-life case of a process which is frequently performed in any company. KanBo provides real-time collaboration as well as communication between IT and business users, document and feedback sharing – everything a team needs to accomplish its goal and create a software.

You can get access to KanBo Sandbox – our demo environment containing exemplary Board of developing software. Do not hesitate and get it for free here.

$(".elementWaiting").hide(); $(".elementWaiting").delay(3000).fadeIn(100);
Advertisment ad adsense adlogger