During a sprint, I generally avoid scope creep. If a change request is small and doesn't impact the sprint goal, the team can discuss and decide if it can be included. If the change is significant, it goes into the product backlog to be prioritized for a future sprint.

During a sprint, I generally avoid scope creep. If a change request is small and doesn't impact the sprint goal, the team can discuss and decide if it can be included. If the change is significant, it goes into the product backlog to be prioritized for a future sprint.
Agile ceremonies are recurring meetings within a sprint to facilitate communication, planning, and continuous improvement.
* **Sprint Planning:** The team decides what work to complete in the upcoming sprint. They discuss user stories, estimate effort, and define the sprint goal.
* **Daily Stand-up:** A brief daily meeting where the team shares progress, identifies roadblocks, and coordinates efforts. Each member typically answers: What did I do yesterday? What will I do today? Are there any impediments?
* **Sprint Review:** The team demonstrates the completed work to stakeholders, gathering feedback and ensuring alignment with expectations.
* **Sprint Retrospective:** The team reflects on the past sprint, identifying what went well, what could be improved, and defining action items to enhance future performance.
I would assess the organization's context, choose a suitable scaling framework like SAFe or LeSS based on needs, implement it incrementally with training and coaching, focusing on value delivery, and continuously inspect and adapt the implementation based on feedback and results.
"In one project, we underestimated the complexity of integrating a new third-party API. This caused us to miss our sprint goal. To address this, we immediately re-estimated the remaining work, broke down the integration into smaller, more manageable tasks, and increased communication with the API vendor. We also temporarily shifted team focus to prioritize the integration, delaying a lower-priority feature for the next sprint. Finally, in the sprint retrospective, we implemented a better vetting process for third-party integrations to avoid similar issues in the future."
Kanban focuses on visualizing workflow, limiting work in progress (WIP), and continuous flow. Scrum uses time-boxed iterations (sprints) with specific roles (Scrum Master, Product Owner, Development Team) and events (sprint planning, daily scrum, sprint review, sprint retrospective).
Use Kanban when you need continuous delivery, have evolving priorities, and want to improve workflow incrementally. Use Scrum when you need structured development with fixed-length iterations, have clear goals for each iteration, and benefit from team collaboration with defined roles.
Correlation is a statistical measure that indicates the extent to which two variables fluctuate together, while causation implies that one variable directly affects or causes a change in another variable.
The different types of data analysis are:
1. Descriptive Analysis
2. Diagnostic Analysis
3. Predictive Analysis
4. Prescriptive Analysis
5. Exploratory Analysis
A pivot table is a data processing tool that summarizes and analyzes data in a spreadsheet, like Excel. You use it by selecting your data range, then inserting a pivot table, and dragging fields into rows, columns, values, and filters to organize and summarize the data as needed.
Some common data visualization techniques include:
1. Bar Charts
2. Line Graphs
3. Pie Charts
4. Scatter Plots
5. Histograms
6. Heat Maps
7. Box Plots
8. Area Charts
9. Tree Maps
10. Bubble Charts
Data analysis is the process of inspecting, cleaning, and modeling data to discover useful information, draw conclusions, and support decision-making. It is important because it helps organizations make informed decisions, identify trends, improve efficiency, and solve problems based on data-driven insights.
1. bit stuffing
2. LRC
3. CRC
4. parity check
here 1 2 3 are either error detection or error correction
which can be potentially done by DataLink Layer
But bit stuffing (from wikipedia) seems to be done by the
physical layer so that the data arrives at the device
synchronized... (i am not sure of the working but i am sure
that it is a layer1 concept)
LRC is not done by Data Link Layer.
Reason- Bit stuffing is used in DLL to identify the new frame and the older frame which is recognized by adding 0111 at the end of every frame so that receiver will get idea that from this moment new frame will start.
Regarding CRC is used for to check whether data is altered during transmission or not and parity is also doing the same.
So remaining is LRC which is not present at DLL at all.
Hi,
As per the client requirement,they will give the columns
then we need to create the custom interface table and
custom base tables
if any queries please let me know
Thanks & Regards,
Siva
The link layer, also known as the Data Link layer, is the second layer of the OSI reference model. It is responsible for node-to-node data transfer and error detection and correction. Its main functions include framing data packets, managing access to the physical medium, and ensuring reliable communication between directly connected devices. It also handles MAC (Media Access Control) addressing to identify devices on the same network segment.
CSMA/CD is a media access control mechanism used in Ethernet
to recover from frame collision. The following steps are
followed to recover from a collision.
Step 1: Before an Ethernet device sends a frame on the
Ethernet cable, it listens to find if another device is
already transmitting a frame (Carrier Sense).
Step 2: Once the device finds that other devices are not
transmitting any frame, it starts transmitting the frame. If
two devices detect that the Ethernet cable is free at the
same time, then both will start transmitting the frames
(Multiple Access). This will result in collision.
Step 3: The Ethernet devices while transmitting the frames,
also listen for the collision. (Collision Detect).
Step 4: If they detect a collision, both the devices stop
sending the frame (back off).
Step 5: They retry the transmission after a logarithmic
time-out period. This process is repeated till the frame is
transmitted successfully, for a maximum of 16 times. The
frame is discarded after the 16th retry.
CSMA/CD -Its called the carrier Sense Multiple
Access /Collision Detection
Each interface must wait until there is no signal on the
channel, then it can begin transmitting. If some other
interface is transmitting there will be a signal on the
channel, which is called carrier. All other interfaces must
wait until carrier ceases before trying to transmit, and
this process is called Carrier Sense.
All Ethernet interfaces are equal in their ability to send
frames onto the network. No one gets a higher priority than
anyone else, This is what is meant by Multiple Access.
Since signals take a finite time to travel from one end of
an Ethernet system to the other, the first bits of a
transmitted frame do not reach all parts of the network
simultaneously. Therefore, it's possible for two interfaces
to sense that the network is idle and to start transmitting
their frames simultaneously. When this happens, the
Ethernet system has a way to sense the "collision" of
signals and to stop the transmission and resend the frames.
This is called Collision Detect.