Application Development using Agile/Scrum

Scrum is an agile-based framework that is often used by development teams in the project development process. Scrum helps organize teams from planning to shipment and establishes effective communication between them.

So that the applications that are built can be on target and do not take long, Scrum uses a priority list and deadlines (sprints) for teams to complete their tasks. This process also involves a number of meetings and periodic checks to assess work results. This makes Scrum an effective and efficient solution in the application development process.

Given that today's business development is dominated by technology, application failure is a very high risk thing. This is often the case with applications that are constantly evolving; either because of business needs, compliance, and so on. As far as we are concerned, many companies, especially banking, use a long and tortuous methodology in the process. Not to mention that the main stakeholders who should be tasked with verifying applications often neglect testing, tight schedules, lack of communication, and a number of other factors.

Therefore, we need an appropriate and easy-to-implement methodology for the application development process. So far, Scrum is a fairly effective project management method to be applied to application development.

Memahami besarnya kebutuhan aplikasi yang baik dan tepat sasaran, training ini sangat penting untuk diikuti oleh staf software development. Meski begitu, scrum juga merupakan metode pengelolaan proyek yang universal sehingga bisa diikuti oleh tim divisi lainnya (marketing, dll).

Training materials include:

• Kicking off a project 
• How to perform a root cause analysis 
• How to communicate the benefits of scrum 
• How to host a kick off meeting and definition of done 
  
• How to improve from the start 
  
• The importance of a good initiation 
  
• Establishing stakeholders 
• How to establish stakeholders 
• Examples of stakeholders 
• The importance of stakeholders at sprint review 
• How to establish stakeholders 
• Scrum roles 
• Introduction to scrum roles 
  
• Characteristics of a scrum master, product owner, and development team 
  
• The value of knowing the roles 
• User stories and the product backlog 
• How to write user stories and acceptance criteria 
• How to organise stakeholder meetings 
• How to find common ground on requirements 
• How to manage changing requirements 
• The importance of prioritising the backlog 
• What are story points 
• How to capture stories in meetings 
• Sprint planning 
• How to manage impediments to planning 
• How to prepare for sprint planning 
• The sprint planning meeting 
• How to prepare artefacts needed for planning 
• How to craft the sprint goal 
• First half of the meeting - The what How to estimate user stories 
• Second half of the meeting - The how 
• How to use velocity 
• What is the outcome of sprint planning 
• Release planning velocity 
• Introduction to release planning 
• How to set a release goal 
• How to decide on scope 
• Driven versus date driven release 
• How to prioritise for the release 
• How to use average velocity and calculate number of sprints in release 
• How to run a release planning meeting 
• How to use the release burn down 
• Daily scrum, sprint review and retrospective 
• Introduction to the sprint lifecycle 
• How to choose sprint length 
• What is the frozen sprint backlog 
• The team work on tasks 
• How to remove impediments 
• How to carry out product backlog grooming and estimation 
• Avoiding carry over 
• How to run the daily scrum 
• How to use the sprint burndown 
• How to run the sprint review 
• What is the potentially shippable increment 
• How to run the sprint retrospective

After participating in this training, participants will be able to understand the benefits of Scrum according to their respective positions, and be able to manage their duties and responsibilities within the team.