- What Are The Different Phases Of SDLC?
SDLC stands for Software Development Life Cycle, It can be divided in to 7 phases
- Planning and Requirement Analysis
- Conduct product feasibility study in the economical, operational and technical areas
- Identification of the risks associated with the project is also done in the planning stage
- Defining Requirements
- Clearly define and document the product requirements and get them
approved from the customer or the market analysts. This is done through
an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
- Designing the Product Architecture
- SRS is the reference for product architects to come out with the best architecture for the product to be developed
- Create Design Document Specification
- A design approach clearly defines all the architectural modules of the
product along with its communication and data flow representation with
the external and third party modules (if any). The internal design of
all the modules of the proposed architecture should be clearly defined
with the minutest of the details in DDS.
- Building or Developing the Product
- In this stage of SDLC the actual development starts and the product is built
- Testing the Product
- Deployment and Mainteance
- What is Agile Methodology?
- It is a practice that promotes continuous iteration of development and testing
- Both development and testing activities are concurrent unlike waterfall model
- The customer has early and frequent opportunities to look at the product and make decision and changes to the project
- Development process is iterative, and the project is executed in short (2-4) weeks iterations. Planning is very less.
- At the end of every sprint, user acceptance is performed
- Speedy and continuous delivery of the software ensures customer satisfaction.
- What are the different types of Agile Methodologies?
- There are several types of agile development methodology. Scrum is one of the most popular and widely used agile methods. Other types of agile development methodology are; development like Crystal Methodology, DSDM(Dynamic Software Development Method), Feature-driven development(FDD), Lean software development and Extreme Programming(XP).
- What is Scrum?
- Scrum is an agile project management methodology or framework used primarily for software development projects with the goal of delivering new software capability every 2-4 weeks.
- Who Uses Agile Scrum Methodology?
- Scrum is widely used by software development teams. In fact it's the most popular agile methodology. According to the 12th annual State of Agile report, 70% of software teams use Scrum or a Scrum hybrid
-
-
- What are the Benefits Received from the Scrum Methodology?
- Organizations that have adopted agile Scrum have experienced:
Higher productivity
Better-quality products
Reduced time to market
Improved stakeholder satisfaction
Better team dynamics
Happier employees
-
- What Are the Components of Agile Scrum Development?
- The Scrum Team
Scrum teams are typically composed of 7 +/- 2 members and have no team leader to delegate tasks or decide how a problem is solved. The team as a unit decides how to address issues and solve problems. Each member of the Scrum team is an integral part of the solution and is expected to carry a product from inception to completion. There are three key roles in a Scrum team:
The Product Owner
The Product Owner is the project's key stakeholder - usually an internal or external customer, or a spokesperson for the customer. There is only one Product Owner who conveys the overall mission and vision of the product which the team is building. The Product Owner is ultimately accountable for managing the product backlog and accepting completed increments of work.
The ScrumMaster
The ScrumMaster is the servant leader to the Product Owner, Development Team and Organization. With no hierarchial authority over the team but rather more of a facilitator, the ScrumMaster ensures that the team adheres to Scrum theory, practices, and rules. The ScrumMaster protects the team by doing anything possible to help the team perform at the highest level. This may include removing impediments, facilitating meetings, and helping the Product Owner groom the backlog.
The Development Team
The Development Team is a self-organizing, cross-functional group armed with all of the skills to deliver shippable increments at the completion of each sprint. Scrum broadens the definition of the term "developer" beyond programmers to include anyone who participates in the creation of the delivered increment. There are no titles in the Development Team and no one, including the ScrumMaster, tells the Development Team how to turn product backlog items into potentially shippable increments
- Scrum Events (Ceremonies)
-
-
- The Sprint
A sprint is a time-boxed period during which specific work is completed and made ready for review. Sprints are usually 2-4 weeks long but can be as short as one week.
Sprint Planning Sprint
Planning team meetings are time-boxed events that determine which product backlog items will be delivered and how the work will be achieved.
The Daily Stand-up
The Daily Stand-up is a short communication meeting (no more than 15 minutes) in which each team member quickly and transparently covers progress since the last stand-up, planned work before the next meeting, and any impediments that may be blocking his or her progress.
The Sprint Review
The Sprint Review is the "show-and-tell" or demonstration event for the team to present the work completed during the sprint. The Product Owner checks the work against pre-defined acceptance criteria and either accepts or rejects the work. The stakeholders or clients give feedback to ensure that the delivered increment met the business need.
The Retrospective
The Retrospective, or Retro, is the final team meeting in the Sprint to determine what went well, what didn't go well, and how the team can improve in the next Sprint. Attended by the team and the ScrumMaster, the Retrospective is an important opportunity for the team to focus on its overall performance and identify strategies for continuous improvement on its processes.
- Scrum Artifacts
- Product Backlog
The product backlog is the single most important document that outlines every requirement for a system, project or product. The product backlog can be thought of as a to-do list consisting of work items, each of which produces a deliverable with business value. Backlog items are ordered in terms of business value by the Product Owner.
Sprint Backlog
A sprint backlog is the specific list of items taken from the product backlog which are to be completed in a sprint.
Increment
An Increment is the sum of all product backlog items that have been completed since the last software release. While it is up to the Product Owner to decide on when an increment is released, it is the team's responsibility to make sure everything that is included in an increment is ready to be released. This is also referred to as the Potentially Shippable Increment (PSI).
- Risk Management
- Resource Risk
- Scope Risk
- Schedule Risk
- Four Method for Risk Management
- Risk Identification
- Risk Quantification
- Risks can be evaluated based on quantity. Project managers need to
analyze the likely chances of a risk occurring with the help of a
matrix.
- Using the matrix, the project manager can categorize the risk into four categories as Low, Medium, High and Critical.
- Risk Response
- Risks can be avoided
- Pass on the risk
- Take corrective measures to reduce the impact of risks
- Acknowledge the risk
- Risk Monitoring and Control
- Risks can be monitored on a continuous basis to check if any change is made. New risks can be identified through the constant monitoring and assessing mechanisms.
- Gantt Chart
- Gantt chart is a type of a bar chart that is used for illustrating
project schedules. Gantt charts can be used in any projects that involve
effort, resources, milestones and deliveries.
- Gantt charts allow project managers to track the progress of the entire project. Through Gantt charts, the project manager can keep a track of the individual tasks as well as of the overall project progression.
- Microsoft Project is one of the key Gantt chart tools used today
- N-tier Architecture
- N-tier architecture is a client-server architecture concept in software engineering where the presentation, processing and data management functions are both logically and physically separated. These functions are each running on a separate machine or separate clusters so that each is able to provide the services at top capacity since there is no resource sharing. This separation makes managing each separately easier since doing work on one does not affect the others, isolating any problems that might occur.
- Presentation layer (Client Tier)
- Application layer (Business Tier)
- Database layer (Data Tier)
- SDD (Software Design Document)
- The software design document (SDD) typically describes a software product's data design, architecture design, interface design, and procedural design
- SAD (Software Architecture Document)
- A software architecture document is a map of the software. We use it to see, at a glance, how the software is structured. It helps you understand the software’s modules and components without digging into the code. It’s a tool to communicate with others—developers and non-developers—about the software.
- The software architecture document provides a comprehensive overview of the architecture of the software system. It serves as a communication medium between the software architect and other project team members regarding architecturally significant decisions which have been made on the project.
- WBS (Work Breakdown Structure)
- Dividing complex projects to simpler and manageable tasks is the process identified as Work Breakdown Structure (WBS)
- In WBS, much larger tasks are broken down to manageable chunks of work. These chunks can be easily supervised and estimated.
- Following are a few reasons for creating a WBS in a project:
- Accurate and readable project organization.
- Accurate assignment of responsibilities to the project team.
- Indicates the project milestones and control points.
- Helps to estimate the cost, time and risk.
- Illustrate the project scope, so the stakeholders can have a better understanding of the same
No comments:
Post a Comment