Immersing Ourselves in Agile

After a full month at Titansoft as interns, we have come to learn more about Titansoft’s Agile culture. So, what is Agile software development?

Waterfall v Agile

Agile is often compared to the traditional Waterfall methodology where a linear approach is taken with software development; each stage is generally finished before the next one can begin. On the contrary, Agile methodology emphasizes the rapid delivery of an application in complete functional components, with a high commitment level from the client throughout the project. With Agile, all tasks are “time-boxed” into phases called “sprints”.

In Titansoft, each sprint lasts a week within which a running list of deliverables planned at the start of the sprint is completed. Deliverables are prioritized according to their value as agreed by the stakeholder and product owner. If all planned tasks for the current sprint cannot be completed in time, work is reprioritized and the information is used for future sprint planning.

For a more in-depth comparison of Agile and Waterfall, Segue Tech’s article makes for a good read: https://www.seguetech.com/waterfall-vs-agile-methodology/

In Titansoft, we use a subset of Agile methodology called Scrum and practice the four scrum ceremonies:

  • Sprint planning: A planning meeting involving the entire team to determine what to complete in the coming sprint.
  • Daily stand-up: Also known as a daily scrum, a 15-minute mini-meeting for the team to synchronise activities and create a plan for the upcoming 24 hours.
  • Sprint demo: A sharing meeting where the team shows what they have completed in that sprint.
  • Sprint retrospective: A review of what did and did not go well, planning improvements and actions for the next sprint.

As mentioned in our previous post, we are working to develop Titansoft’s Training System (TTS), adopting Scrum to better organise the process. At the start of every sprint, two sprint planning sessions are held. The first sprint planning session is meant for the team to come up with user stories for that sprint and manage the current stories left. The second sprint planning session involves consolidating these user stories, choosing which stories to focus on for that sprint, assigning sizes (based on task complexity) to the story and then breaking that user story into tasks. These tasks are then delegated amongst the team members and work begins.

One of the components of the Scrum framework is our “daily standup”, where we come together to discuss what was done the previous day, the challenges we faced, and what we intend to complete today. Towards the end of the week, a retrospective session is held to reflect on things that were done right, and things that were not. This is an important practice of Scrum as teams get to identify what works for them and aspects that can be improved upon.

Here at Titansoft, development teams are given the flexibility and freedom to work within their comfortable schedules. This gives them responsibility to finish the task as well have quality time for themselves.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s