Agileand DBMS
Agileand DBMS
Agile methodology:
Scrum:
Scrum is the specific, framework used under the Agile umbrella to develop
complex products. The term scrum is also used to describe the daily,
standup meetings that occur during a sprint. Scrum prescribes for teams
to break work into goals to be completed within time-boxed iterations(
sprints ).
Crystal Methodology:
It mainly focuses on individuals and their interactions rather than
processes.
Each sprint begins with a planning meeting. During the meeting, the
product owner (the person requesting the work) and the development team
agree upon exactly what work will be accomplished during the sprint. The
development team has the final say when it comes to determining how
much work can realistically be accomplished during the sprint, and the
product owner has the final say on what criteria need to be met for the
work to be approved and accepted.
• backlog
• Burn down charts
• User stories (A user story is an informal, general explanation of a
software feature written from the perspective of the end user. Its
purpose is to articulate how a software feature will provide value
to the customer.)
Sprints are time-boxed periods of one week to one month, during which a
product owner, scrum master, and scrum team work to complete a
specific product addition. During a sprint, work is done to create new
features based on the user stories and backlog. A new sprint starts
immediately after the current sprint ends.
Jira
1. Projects: They are used to organize and manage work within Jira.
Each project contains a set of issues and can have its own custom
fields, workflows, and permission schemes.
2. Issues: They are the primary unit of work in Jira. They represent
tasks, bugs, and other work items that need tracking and
managing. Issues can be assigned to individuals or teams with
various attributes like priority, status, and due date.
3. Workflows: They define the lifecycle of an issue, including its
status and transitions. Jira has a default workflow, but it can also
be customized to match the needs of a specific project.
6. Epics: Epics are large work items that are broken down into
smaller issues. They provide a high-level view of the work that
needs to be done and help teams to prioritize their work.
Database management:
Certainly! Here are some common technical interview questions related to database
management along with their answers:
Normalization
- **Answer:** Normalization is the process of organizing data in a database to reduce
redundancy and dependency, thereby improving data integrity. It involves dividing large
tables into smaller, related tables and defining relationships between them.
Normalization helps eliminate data anomalies and ensures efficient storage and
retrieval of data.
DB queries
Sure, here are some example queries using various database constraints:
6. **Dropping a Constraint**:
```sql
ALTER TABLE Employees
DROP CONSTRAINT FK_DepartmentID;
```
7. **Enabling/Disabling Constraints**:
```sql
ALTER TABLE Orders
DISABLE CONSTRAINT FK_ProductID;
Joins in DB:
Joins are used to combine rows from two or more tables based on a related column
between them. Common types of joins include INNER JOIN, LEFT JOIN, RIGHT JOIN,
and FULL JOIN. Here's an example of an INNER JOIN:
These SQL concepts and operations are fundamental to database querying and
manipulation.