SDLC

BASICS:

IMPORTANT:

TOOLS:

PURPOSE:

Charles Proxy

  • Meant for Mobile Testing

What is it?

  • Process used by software companies to develop and test high quality software.

Software, Development, Life, Cycle

PRODUCTION:

Development:

  • Starts once the design requirements are completed.
  • Software will now be designed into code

Testing & Bug fixing:

  • Your job
  • Testers test output with the requirements
  • Identify issues
  • See how the requirements are acting

Design:

  • Make your research look nice
  • Putting pieces together
  • How things work together

Deployment:

  • Once the product is tested and freed from any bugs
  • This is ready to go
  • Everyone has a say

Requirements:

  • Information and requirements are gathered
  • User requirements, and system requirements

Idea:

  • Brainstorming Idea to solve a problem

Team sport:

  • Every one has a say
  • The whole team comes together

**Maintenance:

  • There are things we need to change
  • Simple maintenance things
  • Customer feedback

REQUIREMENTS:

AGILE:

Why?

  • Allows you to communication with your team
  • Team feedback
  • Let's you adjust along the way

SCRUM:

Definition:

  • A team tactic to move the ball (product)
  • They come together with planning
  • The idea of who does what
  • Has specific way
  • Done in an Agile Way

Definition:

  • Agile is a workflow style.
  • Taking small bits to building something big overtime
  • Being flexible
  • Focus on small pieces
  • Small bits to build something overtime

SPRINT:

Definition:

  • Are from 1-3 weeks
  • Predict what happens at the end of the week
  • Weekly goals
  • Team plans a sprint to succeed in a week.

Consists:

  • Narrow a large clump of backlogs
  • Narrow into a small order
  • Decide before a sprint on these items
  • A sprint is a calender

Idea:

  • Get better everytime with a sprint
  • Put things in the right order
  • Bite off something we could chew
  • Show a demo what you did
  • Review what was made
  • Sprint is filtering Product backlog into
    small incroments. Sprint is filtration.
  • Sprint is a calander

Planning:

Info:

  • Look at the team, and who can do what
  • No doing things independently
  • Mobile developer, Back-end developer, assign jobs
  • Light up different members of the team
    by making them come together
  • Figure out the order of things

QA DURING PLANNING:

  • Risk Analysis
  • Type of testing



START-UP:

  • New companies chase the money
  • Don't care about planning
  • Start cooking

USER STORY:

Refinement:

  • We're the users of the product
  • Open discussion with the product owner
  • Conversation

Backlog Refinement:

  • Remove stories
  • Create new user stories
  • Prioritize stories
  • Move items at the top of backlog for delivery
  • Filled with things we want to do
  • See what you need to work on
  • Stories are created by developers

Story Point:

  • Use in Agile development
  • Define how difficult something is
  • Senior person will do something faster on this

Structure:

    1. you have requirements
    1. put the requirements in the user story
    1. you have a group of gathered user stories - Backlog
    1. move those storypoints out of the backlog for the sprint
    1. Find user stories in the Storypoints
      = 6. Find out how many storypoints can your team do in a sprint
    1. Find how many storypoints you can do in a plan.
      maybe 60-70 storypoints? A storypoint is a user of measurement for how long you can do a sprint for.

JIRA

PLANNING ON JIRA Jira Example





Jira Example 2

SPRINT Planning:

  • The Update that gets the most money is priority,
  • Ask questions on behalf of users (think ahead)
  • QA Job is RISK Reduction.

SCOPE:

  • What is the goal for this Sprint?
    (Learn SDLC and Agile processes)
  • Who is available for this Sprint?
    (Team)
  • What to include?
  • Team confidence?

SCRUM Meeting:

  • What did you do yesterday?
  • What will you do today?
  • Do you have any blockers?

BLOCKER:

  • Can't work on it because someone didn't do their weight and it blocks you from doing your work.

DEMO Meeting:

  • Demo Meetings show what a team has got.
  • Shows a usable piece of software for stakeholders.
  • QA shows documentation, or deployment.

Retrospective:

  • Find the ways that work for you and DO THOSE.

  • Do a demo for every Sprint.


  • What Success have we had?

  • What mistakes have we made?
  • What can we do to improve our process in the future?