Be Agile using Scrum Framework in App Development

Source : https://monday.com/blog/wp-content/uploads/2019/10/Introduction-to-Agile.png

Agile? What is That?

Agile Manifesto

  • Individual and Interactions Over Process and Tools

Team work is powerful tool to build something. Interaction between each people in the team is important thing because we can combine all the idea from each people to be something useful stuff that can help the developm
ent.

  • Working Software Over Comprehensive Documentation

As the meaning is move quickly, we need to make a working software first to make a frequent deployment cycle, if we target to make a comprehensive documentation, we need more time to do it.

  • Customer Collaboration Over Contract Negotiation

Customer is crucial in agile because customer will give continuous feedback to your application, so your application quality will be better and also grow bigger.

  • Responding to Change Over Following Plan

New idea can come up at any time, so we need to be able respond that new idea and make a new change if necessary.

Agile Principle

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Scrum

In scrum, the team consists of 3 parts:

  • Scrum Master

Scrum master is a person that will be your team couch and keep your team in the right track while develop and deliver the products.

  • Product Owner

Product Owner is a person that responsible to list all of the product requirements and split it to the product backlog

  • Developers

Part of the team that implement the requirement and do incremental update to the product each cycle.

In this framework, we need to do five main events, there are :

  • Sprint Planning, in this event, the whole scrum team will define the sprint goal with the stakeholders. After that they measure the weight of each backlog and choose what backlog and sprint goal will they take. Usually, they pick a backlog that has high priority and pick the goal that has high value for the stakeholders. And after that they break the backlog of the requirements into small parts and discuss a plan for delivering the task together.
  • Daily Scrum, in this event, the team will held short meeting to discuss about the problem and progress from each person in the development team toward the sprint goal, adapt to the Sprint Backlog, and also adjust their upcoming work plan. Usually, each person of the team will be asked with this three questions: what has been done, what next, and what kind of problem in the development.
  • Sprint, this is the part where the development team do their increment according to the plan that they discuss in the Sprint Planning.
  • Sprint Review, this part will be held in the last day of the sprint. Usually, in this event the stakeholders will be present and the team will show their progress and demoing the app. By doing this, the team will get some feedback from stakeholders.
  • Sprint Retrospective, we will do some reflections about the sprint. We will evaluate any kind of problem that happened in the last sprint and try to reflect to the past sprint and improve the quality of next sprint.

Usually, Sprint will be done for 2 weeks.

Scrum In My Project

Sprint Planning

Sticky Notes
Discussing Each Backlog Story Point

Daily Scrum

Sprint

In the board we split the component of the backlog in to 4 state :

  • Open : For New Component of The Backlog
  • To Do : For Assigning the Component
  • Doing : For Telling that component is in progress
  • Closed :For Telling that component has done

Sprint Review

Sprint Retrospective

Good, Bad, Start, Stop Boards

References

http://agilemanifesto.org/iso/en/principles.html

http://agilemanifesto.org/iso/en/manifesto.html

https://en.wikipedia.org/wiki/Agile_software_development

Computer Geek's from Jember, East Java, Indonesia