Home

3 simple ways to get started with Scrum

Even though Agile Software development of Scrum is prevalent in Software Industry today but still many teams haven’t been able to make the switch to Agile. The reason are various from not being mandated by their organization or client to not being able to understand it properly or its benefits.
It can be an arduous task if you are starting to follow Agile and there is no guidance for you or may be the new jargons makes your head spin. The way we can solve this easily is by at least starting on the path. As they say a journey of thousand miles begins with one step.
Here are 3 items that you can start with if you want to go Agile and if you implement them right, you will definitely see improvements in your development process.

  1. Product Backlog: – Product backlog can be thought of as a box which contains every single feature that you want to develop within the product/project and any ancillary features as well. Even simpler way of putting it is, it can be thought of as a ‘to-do’ list of your project. The most important feature of PB is that it’s a prioritized list of features, i.e. what needs to be completed first is on top of the list. It can contain new features, bugs, technical work, prototypes, etc.
  2. Daily Standup Meetings: – These meetings are conducted daily with the entire team. Preferably these meetings should be done first thing in the morning. The During the meeting 3 questions are answered by every team member
    1. What you did yesterday?
    2. What you plan to do today?
    3. Are there any obstacles?

    The meetings should end within 15 minutes and technical issues should not be discussed within this meeting.

  3. Sprint: – Sprint is a set period during which pre-decided work has to be completed. There are 3 important features of a sprint
    1. Set Period: – Sprints are time bound. 1 week or 2 week sprints are popular in industry. Work has to be completed within this duration and sprint time cannot be extended.
    2. Pre-decided work: – The work to be completed within a sprint is decided by the team. The team picks up items from the product backlog and decide which items can be completed within the duration of a sprint.
    3. Completed: – The work taken in a sprint needs to be ‘done’ in all respects i.e. analysis, coding, testing, deployment. The development work that is done should be good enough to be deployed on production.

    There are several other items involved in Scrum, however these 3 things will get you started nicely and will inculcate Agile development habits in you, which can later be enhanced.

Facebook Twitter Linkdin
Up ArrowBack to Blog

Big Data for Developers – What it is and what it’s not?

Storage Management in The Days of Cloud