Скачать или смотреть SCRUM and the app development process (full video)

Part 1: What is SCRUM?
Have you ever heard of the term Scrum? I bet you're thinking of a rugby field with men huddled together, scrambling for a ball, right? Well, SCRUM is also an agile, effective and efficient way of developing and sustaining complex software products which App Inlet has adopted.

The old school way of development is called the Waterfall Model, which
is used to organise and deliver software in consecutive phases.
In the Analysis phase, an analyst gathers the requirements.
Then it’s the design phase (also known as the wireframe stage): This is when code and other artefacts are planned and modelled.
Implementation phase: The designs are used to build the product.
In the Testing phase: Testers ensure that the product meets a high degree of quality.
Finally the product is released to the public.

Thereafter, there is ongoing support and maintenance in a live environment.
SCRUM consists of self-managing, cross functional teams, which means that the teams consist of a group of people, who each have different areas of expertise, but work together for the same outcome.

The teams work in iterations, giving the business the flexibility to change their requirements, while providing the development team with the necessary time to deliver a working piece of the product.

SCRUM allows clients to give their input during the course of production rather than having a backlog of adjustments to amend at the end of the process, right when we think we're done, which the Waterfall Model fails to provide.



Part 2: SCRUMs 3 principles
In this video, we will dive a little deeper into the process theory that we use to develop apps... which is called SCRUM. Scrum consists of 3 principles, namely: Transparency, Inspection, and Adaption.

Transparency: The Scrum team all agree to be honest in all that they do on a project. Meaning that functionality is not done until it meets the team's definition of done. There is no "almost done" in SCRUM, there's done and not done.
Inspection: This is the principle of ensuring that the team consistently checks up on progress and makes improvements based on what they have seen.
Adaptation: This relates to the continuous improvements in practices whilst sticking to values and nurturing effective communication.

By following the three principles of SCRUM, we are able to design and build complex solutions for our clients as a trustworthy and flexible team.



Part 3: SCRUMs terminology
We are now going to explain some "SCRUM" terminology involving "SPRINTS".

Sprints are not just things that happen when you move your legs really fast... they are also what happens when SCRUM teams move their fingers really fast. The App Inlet’s SCRUM team work in sprints of two weeks to complete a set amount of work.

Sprint Planning: defines what must be delivered in the sprint, how it will be achieved and who it will be assigned to.
Sprint Backlog: consists of all the upcoming projects which need to be planned by the team.
In Sprint Reviews the client is shown the achieved work of the entire team: designers, developers, and the product owner.
Sprint Retrospective: The SCRUM team meet to reflect on the work done in the sprint so they can improve and make changes before they begin the next sprint.

Thereafter, the whole process starts again for the next sprint. This system of development ensures that developers are consistently improving and communicating the different areas of improvement before, during and after the release of the product. Making sure that the client is always aware of what is going on and is happy with their product.



Part 4: SCRUMs roles
In this video we will introduce the different roles involved in the development process we use… which is called Scrum.

There are three roles within our “Scrum” environment: Product Owner, Scrum Master and the Development team members.

The three roles describe the key responsibilities for those on the scrum team. This allows teams to take responsibility for how they organise themselves and allows collaboration for improvement.

The product owner does not own the client’s app… they are the champions of the project and ensure the client's vision is made into a reality.
The Scrum Master is in charge of ensuring that the app development process is in alignment with Scrum best practices.
The development teams are made up of designers and developers who work together daily to create magical digital solutions that look and work beautifully.

Together the Scrum team will keep your project and moving in the right direction.