OSSCube - BP Agile SDLC - PowerPoint PPT Presentation

About This Presentation
Title:

OSSCube - BP Agile SDLC

Description:

BP Agile SDLC - An Efficient Approach to Software Requirement Gathering and Tracking. – PowerPoint PPT presentation

Number of Views:65
Slides: 25
Provided by: Username withheld or not provided

less

Transcript and Presenter's Notes

Title: OSSCube - BP Agile SDLC


1
OSSCube BP Agile SDLC
2
What is BP Agile SDLC ?
BP Agile SDLC stands for Business Process
Agile Software Development Life Cycle
3
In next 1 Hour
4
Challenges
The Challenges faced at different roles
5
Why not Standard SDLC ?
Why Standard SDLC like Waterfall and Agile were
not giving the desired solution ?
6
And we devised the solution
7
And we devised the solution
8
Why BPMN ?
9
How Process Modeling Works?
10
Why Prototype?
11
BP Agile SDLC
12
BP Agile SDLC
  • Business Analyst /Project Manager captures major
    business flows using BPMN
  • BPMNs are sent to Customer for approval after
    tested and validated by QC
  • BAs create Prototypes for all approved BPMNs
  • QC validates and approves Prototypes and these
    are sent to Customer for approval
  • Along with the functional requirement gathering,
    BA also captures the non-functional requirements.
  • Project Manager creates Master Sprint Plan and
    Cost Estimates Based on the approved features,
    BPMNs and Prototypes
  • Master Sprint Plan and Estimates are sent to
    Customer for approval

13
Phase 0 Sign-Offs
  • In BP-Agile Phase 0 is extensive and project team
    gets approvals and Sign-Offs on following
    documents at the end
  • BPMNs on the major Features/Business Flows
  • Prototypes
  • Non Functional Requirements
  • Master Sprint Plan
  • Cost Estimates

14
BP Agile SDLC
15
BP Agile SDLC
  • PM creates Sprint Plan based on approved Master
    Sprint Plan
  • Engg. Team update the BPMNs and Prototypes to
    capture the field level details for stories In
    Scope
  • These are further validated by QC and then send
    for Customer Sign Offs
  • Engg. Team writes code for the Stories as per
    approved BPMNs and Prototypes
  • QC tests the developed stories with reference to
    BPMN and Prototype
  • Test cases written only for Integration,
    Negative Scenarios
  • QC send release video and note for Customer
    review
  • Customer feedback is included in Sprint Backlog
  • Project Team conducts Retrospective to discuss
    What Went well What Could Have been Better and
    Action Items

16
Sprint 1 Sign-Offs
  • In BP-Agile Phase 1 is project team gets
    approvals and Sign-Offs on following documents at
    the end of each sprint
  • Sprint Plan and Time Estimates for visual sprints
  • Field level Updated BPMNs and Prototypes
  • Release Notes

17
BP Agile SDLC
18
Example PO Process
19
Principle Behind BP-Agile SDLC
20
Salient Features
21
Results

22
Reference BPMN
  • Business Process Model and Notation (BPMN) is a
    graphical representation for specifying business
    processes in a business process model.
  • Business Process Management Initiative (BPMI)
    developed BPMN, which has been maintained by the
    Object Management Group since the two
    organizations merged in 2005.
  • Version 2.0 of BPMN was released in Jan 2011
  • A standard Business Process Model and Notation
    (BPMN) will provide businesses with the
    capability of understanding the business
    procedures in a graphical notation and will give
    organizations the ability to communicate these
    procedures in a standard manner
  • Furthermore, the graphical notation will
    facilitate the understanding of the performance
    collaborations and business transactions between
    the organizations/departments/roles.

23
  • Q A

24
  • Thanks !
Write a Comment
User Comments (0)
About PowerShow.com