Scrum Crash Course

Scrum offers an alternative to conventional management practices. With the dynamics of business constantly evolving, management techniques have to evolve as well. Before you can implement Scrum, you need to learn more about how it works and the steps it entails. Here is an overview of what you will learn through our Scrum Crash Course:

Epics
Overarching Initiatives: If you think about building a piece of software or a website, this could represent an entire page. Stories are associated with Epics. A good epic is defined by all the stories that will accomplish the goal.

Tips: A good way to think of an Epic is as a set of features that would accomplish a specific goal for the project. When thinking of epics, you may think of milestones. Each project is different, so it will take some practice to get good at breaking projects down into meaningful parts.

Stories
A story is like a task but is told as a story.
For example:
“As a user, I can update my password and save it to my account”
Remember, this is about good communication, so try to include images and artifacts to help your teammates understand the intent of the story.
Also, a good story answers all relevant questions upfront. A scrum master and project manager will help with this.

Sprint Planning
A sprint is a block of time. In our case, we work in two-week increments (also known as iterations). Before we kick off a two-week sprint, our scrum team assigned to the project will sit together and pull projects from the icebox and enter them into the backlog to be worked on.

Use the effort points allocated to each story as a mechanism to understand how much work your team may accomplish within a two-week sprint. The sum of the story points your team is able to accomplish within a sprint is called Velocity.

The Sprint
The sprint a sacred block of time that is to be projected at all costs. Once the work has been agreed upon, it is up to the team and the scrum master to work together to achieve the sprint. Teams use meetings, like “The Daily Standup”, and communication tools like Slack to warn each other in case there is a chance that some task will not be completed. The goal of the sprint is to exact all of the work they had agreed upon to either meet or exceed their target velocity.

The Daily Standup
When your team is assembled, and wherever possible, a standup is a 10 to 15-minute block of time where you stand with your team and each person gets a minute or so to discuss:

  1. What they accomplished yesterday
  2. What they hope to accomplish today
  3. Is there anything blocking them

Tip: DO NOT FIND A SOLUTION. Stand-ups tend to take up too much time when we hear a problem and try to find a solution for the problem during the standup. Scrum Masters have to keep the team on task. If a blocker arises or a few team members need to collaborate on something, kindly request that those conversations take place after the standup.

Blockers
A blocker is generally a reference to something that is preventing work from being done. This could be missing information, missing technology requirements, another story/epic that needs to be done first, design artifact or even a client meeting that has not occurred yet.

Dealing with Blockers
Blockers occur often and vary from case to case but you have to overcome them to keep your team moving. There is no one way to deal with blockers except to communicate clearly. Ask good questions that get to the root of what needs to be solved and have laser focus on solving exactly that. Once you feel the blocker has been eliminated, confirm with your team that they are able to move forward.

An enemy of success is assumption.

Velocity
Velocity is the sum of effort points your team is able to accomplish within a given sprint. It is part of the Scrum Master’s agenda to work with the team to achieve the highest velocity possible. Note that there will be certain things that affect your team’s velocity, for example vacations.

The Backlog
The backlog is a set of epics and or stories in order of highest value or customer impact. A backlog should be groomed regularly.

Steps for Grooming a Backlog

  1. There are times our teammates may not be using the backlog to record progress on a story. Encourage them to use the tools provided to your team to make sure stories are kept up to date.
  2. The backlog is sorted by the most important work first, so make sure all the epics and stories are in order.
  3. Make sure stories are well written and provide as much meaning as possible. Think if someone was looking at the story for the first time, can they sort out what needs to be done without needing to ask you a question?
  4. Remove or otherwise delete stuff that is just not going to get done or is redundant.

Sizing
Stories need to be sized for effort. We use a scale of 1,2,3,5 and 8. To size a story, sit with the scrum team assigned to the backlog and go through the stories and size them with the team. Get everyone involved in contributing to the sizing. Your teammates have different experience and visibility into the work you do.

Effort and Points
Effort is not exactly associated with how much time something will take, but the higher the point value allocated to a given task, the more tasking it will be on the team. A good rule of thumb is that if a story scores over 5 points, it should be broken down into more stories.

With Scrum, you can enhance the efficiency and productivity of your team and also make sure that work is completed on time, without conflict, and without compromising on quality. Scrum offers the ideal framework for modern businesses to improve their operations and achieve their goals.

Building Mobile App – Where to Start and What to Do

Before we start, here’s a little heads-up: this post is not for developers or designers with over 67 years of experience. This is a simple introduction on how to get started when you get an idea for an app, but are not sure where to begin. If you feel like saying something or have an advice or a suggestion that would be beneficial, please go ahead and comment below.
So, you have had this amazing idea for an app in your head for days, weeks, months, and you are more than sure that people can’t wait to try it and use it every day and tell their friends all about it. If this sounds like you, read on.
But where do you start? Should you look for a developer and talk to him about it first? Or hire a designer who will transfer your idea into screens of beautiful design? Nope, sorry, but that’s not how it works.

Functionality/Purpose
First, let’s define the purpose of your app. Yes, simply write it down in one sentence. Don’t make it overcomplicated. Simplicity is the key. Here is an example of one of the apps we are working on:
• Functionality: App delivers a new quote every morning for you to read
• Purpose: Inspires you with quotes from famous successful people
What problem is it going to solve? Define your goal and the mission of your app.

Target Audience/User Groups
Nothing is worse than putting in all your time and energy into a beautiful product that no one is using. Know your target audience! Ask yourself who this app is for. Without demand, there is no reason to create something. Be specific, pick your niche and create your product around their needs. Here’s an example with our Quotes app:
Target Audience: Entrepreneur, someone with an idea for a new product, or a start-up

Sketching
Shut Photoshop down right now and just do it. If you are not an app designer with a 3-page portfolio, take a pencil, note pad and start sketching. Otherwise, you are spending your precious time on something you are not an expert on. Let the real app designer handle that part.
For now, put your thought on the paper, and if you feel adventurous, use a wireframing tool (HotGloo, Fluid, or UXPin as an example). Just remember to be as detailed as possible. It doesn’t have to be ideal. Do include the flow of how to navigate your app and show all the features you can think of. Visit Dribbble for some great examples and ideas about design and implementation.

Talk to the Developer
By now you might think that most of the work has been done, but the truth is the actual process is just about to begin. You have to explain your app idea to a developer. Most people think app is all about design. They are wrong: it’s all about how a user is going to experience your app. So, look for a developer who puts user experience first! Also, keep in mind that not everything is possible when it comes to coding and the process takes more time then you think. Good developers should also provide you some suggestions on how to improve your idea, and not just simply follow your orders.

Testing Plan
Releasing your app without testing it first is probably one of the biggest mistakes you can make. Of course, to you, it might seem everything is ready, but don’t rush. Ask your friends or talk to your family about testing it. Let people use it and hear their honest feedback. You will be surprised at how many recommendations you can get and it’s a good thing, as this step might help you identify any UI/UX flaws you haven’t noticed before.
This is just the beginning and there are more steps you need to get through to get your shiny app out there. You and your developer will have to set up the backend of your system, decide how to monetize your app, and create a marketing strategy for it, etc. We will cover all this and more in Part 2 of this article!