Presentation should be 7 to 10 minute oral presentation summarizing SDLC paper. Instructions are given clearly in the PPT. I’ll attach the document below. Please follow those instructions .So the ppt should be done on SDLC paper. I’ll attach the paper too.Every thing should be in format.After each and every slide I need the following slide explanation. Because the slide sold be only of bullet points.If u have any queries plz do text me
executive_summary_assignment_in_class.pptx
8100sdlc.docx
Unformatted Attachment Preview
Dr. Anthony J. Intorelli
Wilmington University
29 February 2019
Agenda
Introduction
Assignment
Presentation Expectation
Concluding Remarks
Assignment
Executive Summary
PowerPoint Presentation
Presentation Delivery
Preparation
7 – 10 Minutes in Length
Presentation Expectation
Slide Format
Do NOT put too much information on a page
Use bullets
Write brief (one line) statement points
Do not use animation or transition effects
Presentation Format
Introduction
Agenda
Main Slides
Concluding Remarks
References and Supporting Documents
Dark lettering on a light background
Be consistent with:
Capitalization
Punctuation
Font
Font size
Presentation Expectation
Presentation Format
Introduction
Agenda
Main Slides
Concluding Remarks
References and Supporting Documents
Presentation Expectation
Presentation Format
Dark lettering on a light background
Be consistent with:
Capitalization
Punctuation
Font
Font size
Presentation Delivery
Seeing
Presentation
Body Language
Speaking
Do NOT read your slides
Use notes
Speak clearly
Eye Contact
Preparation
Plan
Targeted and Focused
Audience Needs
Tell a Story
Flow of Presentation
Practice
Relax
Concluding Remarks
Main Point
Main Point
Main Point
Executive Summary Assignment
Questions
Executive Summary Assignment
Thank you
References
Author Last Name, F.M..
Running head: SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Software Development Life Cycle: Agile Model
Bhavana Bhonagiri
Wilmington University
1
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Software Development Lifecycle Models
There are six common System/Software Development Life Cycle models namely
•
Waterfall
•
Agile
•
Iterative
•
V-shaped Model
•
Spiral Model
•
Big Bang Model
This discussion will centre on the Agile Software Development Life Cycle model in software
development. The discussion will show how the agile model can be applied in a development
environment.
Agile model is a project management approach that allows or advocates for repeated
iteration of testing during the development of software in its lifecycle. In this model of
Software Development Life Cycle testing and development activities are carried out
concurrently. The major strength of Agile or scrum, as many developers call it, is its iterative
approach to development unlike waterfall methodology (Rastogi, 2015). Development takes
place in several stages with the end product of each stage being delivered to the customer
(Kilian, n.d). The advantage of this approach is that customer review or feedback allows
developers to perfect the product during the next stages if such change is needed. The
following are the phases of agile method. These methods were actually applied to develop
staff management software.
2
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Step 1: product Backlog Creation
This is a list that contains all features to be implemented in the project development
process. All items are ordered according to priority. Every item in the order is also known as
a user story. Every user story has a special ID. The following are examples of user stories
ID
User Story
a-001
I want to be able edit tasks by adding or
deleting tasks in employees’ workloads.
a-002
I want to able to use drag and drop features
to add task, change task duration as well as
change starting dates for upcoming tasks.
a-003
I want to assign role to employees in two
methods
Part-time
Full-time
The user stories description should include the following important fields
Importance
Initial estimate
How to demo
Track
3
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Components
Requestor
Bug track ID
After creating the backlog the next step involves sprint planning.
Step 2: Sprint Planning and Backlog Creation
The first step in this stage is to determine the duration of the sprint. Short sprints are
always the best because they allow more often product release which also means customer
feedback will be frequent. This enable the developer to eliminate all errors or bugs before the
final product is released (Rastogi, 2015). Nevertheless sprints can be longer however, it is
important to have optimal sprints because they allow the developers to work well. The most
important aspect is for team members and developers to work together (MaRs, 2006). The
product owner exemplifies the importance of good user stories and the scrum team comes up
with estimated labour costs. The scrum team also selects the best user stories from the
product backlog (MaRs, 2006). Additionally, the team members come up with the best ways
to solve the tasks. The next step involves creating the sprint backlog. The sprint backlog is a
collection of user stories that will be accomplished in the ongoing sprint.
Step 3: Scrum meeting. Working on Sprints
After selecting actual user stories, the developers commence web development. This
stage involves using a task board to track the working process. A task board is merely a table
with five columns each column depicting what is happening to the story at each stage (Kilian,
n.d). The tasks can be numbered with each tasks being laid out to their corresponding column
as shown below
4
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Stories
To do
In progress
Testing
Task 1
Task 2
Task 7
5
Done
Task 16
Task 8
Task 3
Task 6
Task 12
New
Task
Task 17
Task 9
Task 13
Task 15
Task 10
Task 11
Task 14
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Note: This table is used in the development process and is also important in the scrum
meeting where members can discuss the progress of the tasks including the tasks each
member has completed.
Step 4: Product testing and Demonstration
The result of every sprint is a final working product. Full life cycle testing is therefore
important mostly in reducing costs incurred in the testing period. A good way is to reduce the
user stories because many user stories cause too many bugs. Additionally, the scrum team can
also include QA engineers. Demonstration is the end result of every sprint. The development
team therefore produces a review as well as conducts a demonstration of what has been
accomplished, which can be accepted or approved for further development by the
stakeholders (Kilian, n.d).
Step 5: Retrospective Sprint Planning and Next Sprint Planning
Retrospective involves looking at the approaches that were used to deliver the results
and determining which of those approaches are replicable in the next step (MaRs, 2006). The
project team identifies what worked out well as well as what can be improved in the
future/next iteration. Once the improvement methods have been identified, the team moves
on to planning for next sprint.
6
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
Conclusion
The above model is ideal because of its agility as well as progression. Its utmost
strength lies in the constant communication between the stakeholders and the developers.
This constant communication also takes place between team members where they meet, plan
a sprint, identify and share tasks as well as meet again to discuss and iron out problems
experienced in the sprint. The fact that Agile SDLC model allows communication between
members, testing and demonstrations makes it a superior SDLC model.
7
SOFTWARE DEVELOPEMENT LIFE CYCLE: AGILE MODEL
References
Kilian, A., (n.d). Applying Agile to Non-Software Projects. Retrieved on April 12, 2017
https://www.meistertask.com/blog/agile-project-management-non-softwareprojects/
MaRs, (2006). Product development: Using Agile methodology for software development.
Retrieved on April 12, 2017 from https://www.marsdd.com/mars-library/productdevelopment-using-agile-methodology-for-software-development/
Rastogi, V. (2015). Software Development Life Cycle Models-Comparison, Consequences.
International Journal of Computer Science and Information Technologies, 6(1),
168-172.
8
…
Purchase answer to see full
attachment
Recent Comments