Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SDLC Plan
Advanced Progressive
By
Muhammad Nabeel Arif
Software Development
Life Cycle
We are going to follow a 3 step process to develop a complete
software application
Design:...
Plan
Planning phase is the first and very important phase in
our SDLC Plan.
Requirements are obtained from the Product Own...
Requirements
Product Owner provides information in the form of User story, a
sample app to replicate, a website to convert...
Estimates
Based on the requirements a WBS is created to
estimate the time on different platforms (iOS or
Android)
Estimate...
Feedback and Approval
Based upon the Product Owner’s feedback, necessary
changes are made in estimate document.
Tools and ...
JIRA Confluence
https://www.atlassian.com/software/confluence
Develop
Here we start the implementation of the actual
application. This phase includes coding, managing
source code, test...
AGILE
Iterative
Adaptable
Rapid
Cooperative
Quality-driven
Not a process, it's a philosophy or set of
values
Scrum
Scrum is an iterative and incremental Agile software
development framework for managing software projects and
produc...
Scrum Overview
Roles
The Product Owner
The Scrum Master
The Development Team
Responsible for the product backlog
and maximizing the product ROI.
• Represents the users
• Clearly expresses backlog ite...
Responsible for the scrum process
• Removes impediments
• Facilitates scrum events
• Facilitates communication
Responsible for delivering a potentially shippable
increment of working software.
• Self-organized
• Cross functional
• De...
Sprint
A sprint is the basic unit of development in Scrum.
The sprint is a "timeboxed" effort; that is, it is
restricted t...
Artifacts
Product Backlog
Sprint Backlog
Increment
Burn down
Single source of
requirements for any
changes to be
made to the product.
• Living list that is
never complete
• Ordered: v...
Sprint Backlog
Consists of committed PBIs negotiated between the
team and the Product Owner during the Sprint Planning
Mee...
Meetings
Sprint Planning
Meeting
Daily Scrum
Sprint Review Meeting
Sprint Retrospective
Meeting
Backlog Refinement
Meeting
Two part time boxed meeting: 8h/1m sprint.
1. Defines what will be delivered in the increment
• Team selects items from th...
15 minute time-boxed event for the Team
to synchronize activities.
• What has been accomplished since last meeting
• What ...
4 hour time-boxed meeting
• Product owner identifies what has been done
• Team discusses what went well, what problems
ran...
Improves the process.
• Inspect how the last Sprint went
• Identify and order the major items that went we
and potential i...
Backlog Refinement
Refine the requirements, technical limitations and estimates
• It is common to write Product Backlog It...
Used to assess when work is complete on the
product increment.
• Defined by the product owner
• Unique for the whole team
...
Scrum Summary
JIRA & JIRA Agile
https://www.atlassian.com/software/jira/
https://www.atlassian.com/software/jira/agile
Deployment
Complete testing of the application
Fill the test sheets for the app
Fill the Release checklist for the app
Dep...
References
http://agilemethodology.org/
http://scrumreferencecard.com/scrum-
reference-card/
http://en.wikipedia.org/wiki/...
Upcoming SlideShare
Loading in …5
×

Sdlc plan

446 views

Published on

SDLC stands for Software Development Life Cycle. Slides give an overview of the SDLC Plan we used in our organization.

Published in: Software
  • A professional Paper writing services can alleviate your stress in writing a successful paper and take the pressure off you to hand it in on time. Check out, please ⇒ www.WritePaper.info ⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Sdlc plan

  1. 1. SDLC Plan Advanced Progressive By Muhammad Nabeel Arif
  2. 2. Software Development Life Cycle We are going to follow a 3 step process to develop a complete software application Design: Requirement gathering and estimates and approval JIRA Confluence & Google Docs Develop: Code, Test and Demo JIRA, JIRA Agile & Git to manage source code Deploy: Final testing and Deployment JIRA, Play Store, App Store
  3. 3. Plan Planning phase is the first and very important phase in our SDLC Plan. Requirements are obtained from the Product Owner Active involvement of Product Owner is required during this phase to clarify the ambiguities in the requirements. Estimates are finalized against Work Breakdown Structure (WBS)
  4. 4. Requirements Product Owner provides information in the form of User story, a sample app to replicate, a website to convert into mobile format or mock-ups. Requirements are evaluated by the Project Manager who further assigns them to relative developer (iOS or Android) In case of any ambiguity or clash in requirements clarification is requested from project owner In case of technical limitations, alternatives are suggested. According to final requirements, design elements for applications are requested in the form of PSDs
  5. 5. Estimates Based on the requirements a WBS is created to estimate the time on different platforms (iOS or Android) Estimate sheets display complete picture of the app on a specific platform listing time required by each item, assumptions made, limitations, server interaction
  6. 6. Feedback and Approval Based upon the Product Owner’s feedback, necessary changes are made in estimate document. Tools and technologies are agreed for the app. Discussion continues until we get approval from the Product owner. From here onwards starts the develop phase
  7. 7. JIRA Confluence https://www.atlassian.com/software/confluence
  8. 8. Develop Here we start the implementation of the actual application. This phase includes coding, managing source code, testing, demo. We will use following process and technique during this phase. Agile Scrum JIRA , JIRA Agile & Git for managing code
  9. 9. AGILE Iterative Adaptable Rapid Cooperative Quality-driven Not a process, it's a philosophy or set of values
  10. 10. Scrum Scrum is an iterative and incremental Agile software development framework for managing software projects and product or application development. Its focus is on "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach". • Scrum Overview • Roles • Sprint • Meetings • Artifacts • Scrum Summary
  11. 11. Scrum Overview
  12. 12. Roles The Product Owner The Scrum Master The Development Team
  13. 13. Responsible for the product backlog and maximizing the product ROI. • Represents the users • Clearly expresses backlog items • Orders them by value • Ensures visibility
  14. 14. Responsible for the scrum process • Removes impediments • Facilitates scrum events • Facilitates communication
  15. 15. Responsible for delivering a potentially shippable increment of working software. • Self-organized • Cross functional • Developer as title • Defines practices • 4 to 9 persons
  16. 16. Sprint A sprint is the basic unit of development in Scrum. The sprint is a "timeboxed" effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each sprint and is normally between one week and one month, although two weeks is typical
  17. 17. Artifacts Product Backlog Sprint Backlog Increment Burn down
  18. 18. Single source of requirements for any changes to be made to the product. • Living list that is never complete • Ordered: value, risk, priority & necessity • Estimated by the team
  19. 19. Sprint Backlog Consists of committed PBIs negotiated between the team and the Product Owner during the Sprint Planning Meeting Increment The increment is the sum of all the Product Backlog Items completed during a sprint and all previous sprints. Burn Down Indicates total remaining team task hours within one Sprint
  20. 20. Meetings Sprint Planning Meeting Daily Scrum Sprint Review Meeting Sprint Retrospective Meeting Backlog Refinement Meeting
  21. 21. Two part time boxed meeting: 8h/1m sprint. 1. Defines what will be delivered in the increment • Team selects items from the product backlog and defines a sprint goal 2. Defines how the increment will be achieved • Items are converted into tasks & estimated
  22. 22. 15 minute time-boxed event for the Team to synchronize activities. • What has been accomplished since last meeting • What will be done before the next meeting? • What obstacles are in the way?
  23. 23. 4 hour time-boxed meeting • Product owner identifies what has been done • Team discusses what went well, what problems ran into & those that were solved • Team demonstrates what it has done in a demo • Product owner discusses the backlog as it stand • Entire group collaborates on what to do next
  24. 24. Improves the process. • Inspect how the last Sprint went • Identify and order the major items that went we and potential improvements; and, • Create a plan for implementing improvements
  25. 25. Backlog Refinement Refine the requirements, technical limitations and estimates • It is common to write Product Backlog Items in User Story form. In this approach, oversized PBIs are called epics. Break the complex epics into small user stories • The team considers the effort they would expend to complete items in the Product Backlog and provides other technical information to help the Product Owner prioritize them. • Most customers don’t use most features of most products, it’s wise to split epics to deliver the most valuable stories first. • The Backlog Refinement Meeting lacks an official name and has also been called “Backlog Grooming,” “Backlog Maintenance,” or “Story Time.”
  26. 26. Used to assess when work is complete on the product increment. • Defined by the product owner • Unique for the whole team • Must allow immediate release • Quality increases with maturity
  27. 27. Scrum Summary
  28. 28. JIRA & JIRA Agile https://www.atlassian.com/software/jira/ https://www.atlassian.com/software/jira/agile
  29. 29. Deployment Complete testing of the application Fill the test sheets for the app Fill the Release checklist for the app Deploy the app Install and update the deployed app
  30. 30. References http://agilemethodology.org/ http://scrumreferencecard.com/scrum- reference-card/ http://en.wikipedia.org/wiki/Scrum_%28softwar e_development%29

×