RSS

Category Archives: Technical

The posts under this category, exclusively contain the technical related information. It contains information about Computer rlated concepts, engineering, advancements in the technology etc.

Unspoken truth hidden behind my Heart


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

In Life we meet many people who leave their own impressions and memories. Every person have their own importance and everyone holds a piece of our lives puzzle. Even if a person leaves us, we can never be full. When you experience loss, people say you’ll move through the 5 stages of grief….Denial, Anger, Bargaining, Depression, Acceptance. ….. Unfortunately I cycle through all of them all every day.

My Love, Though my words will never find you, I hope that you knew I was thinking of you yesterday, today, tomorrow and everyday to come….. and that I was wishing you every happiness. Love you Always, The girl who loved me and walked with me.

My Heart never knows loneliness until you left me. World never knows that i still wake up thinking of you  each-day .
IMG_20190817_204658.jpg
I miss your company,
I miss your smile,
I miss walking with you in rain,
I miss your love, care, concern,
I miss the sensation of your touch.
I miss you, pampering me like kid,
I miss visiting temples with you,
I miss the arms that protected me,
I miss the shoulder that takes me to sleep,
I miss the fingers, that wipes out my tears,
I miss the hand that holds me when I am down,
I miss holding you at night,
I miss support of your shoulders when I am tired.
I miss feeling like you want me.
I miss early morning walks in the park by holding your hand,
I miss the kiss which you used to give on my forehead daily,
I miss imagining us a year from now,and how happy we should be.
I miss planning our vacations,
I miss phone calls, text messages,
I miss sweet fights  and arguments with you,
I miss daydreaming of how nice it will all be.
I miss the idea of you missing me!!!
I miss everything we used to be!
Finally I miss, my Life’s journey with you,
Nobody Understands how much I miss you,

I Miss You

You are defined as my unspoken truth hidden behind my heart…

The sad part is, that I will probably end up loving you without you for much longer than I loved you when I knew you. Some people might find that strange.
But the truth of it is that the amount of love you feel for someone and the impact they have on you as a person, is in no way relative to the amount of time you have known them.

I will always hold a candle for you – even until it burns my fingers, hand.
And when the light has long since gone …. I will be there in the darkness holding what remains, quite simply because I cannot let go what i experienced and what memories you left with me.

Please feel free to share your lessons you learned, you experienced , you came across in your life in the comments below.

 
Leave a comment

Posted by on September 1, 2019 in Technical

 

SEX vs MAKING LOVE


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

 When researching this topic I came across many opinions on the Internet. The explanations ranged from the obscene to the very simple. Some common themes that kept coming up were:

  1. F||King is hard, hot and nasty and always objectifying. whats-the-difference-between-making-love-and-having-sex
  2. Sex is well – sexy, and can be fast, hard … but also slower, and is often objectifying.
  3. Making-love is slower and gentle, only happens between two people that are in love, have mutual respect, and consider the feelings and pleasure of the sexual partner.

Every woman expects to be protected, looked after and loved as much in bed as in every day life. This is not just a legend used by women to manipulate men. Woman expect her partner to love and care her, but not to see her as a sex toy. It became a job for woman to satisfy her partners sexual needs whether she is ready or not.

Sex is just Physical act. Many term Sex  as “Fucking” which is more about the man and his orgasm (&needs) In General Sex is having physical intercourse between a couple. This is irrespective of the fact that they share love or any bond between them. Sex is all about a sexual intercourse between two people who only share their bodies. Most men are attracted to one-night-stands or, with other words, to having sex. The lack of commitment needed and the easy attaining of the main goal: feeling good, are just two reasons pleading in favor of having sex.

It became very common that Men/Woman are having sex with more than one person in life. Earlier it is limited to Men. But now, along with men, many woman sharing their bed with multiple people for several reasons. One may have sex with any person(spouse, friend, beloved, colleague, stranger) needn’t be their partner, spouse, beloved etc. It can also mean casual sex with anyone. Having sex doesn’t extend beyond sexual intercourse and more often than not, there isn’t any emotion between the couple.  In Sex Emotions not necessarily involved if you are in an uncommitted relationship.

If you’re f*cking, it doesn’t have to be super-sweet and nice. You can even be mean to each other. You can be raunchy and dirty. The filthiest part of you that you want no one to see, except for the person you’re f*cking. Sex is all about a sexual intercourse between two people who only share their bodies. In present world most men/woman are attracted to one-night-stands or, with other words, to having sex. The lack of commitment needed and the easy attaining of the main goal: feeling good, are just two reasons pleading in favor of having sex. F*cking is a space in which partners show different sides of themselves that they may never show in public. This is where sexual taste brings out hidden personality aspects

On the other hand there is so much more between a man and a woman making love. There are feelings and emotions, leading to a totally different connection between the two of them. More than that, for women, one of the most important things during sex is the environment. Communication is essential for great results. Men must pay attention to the unspoken signs every woman gives them. Ignoring these signs will make women feel used. The old legend that says that when a woman says “no” she actually means “yes” is nothing more than a poor excuse so keep your ears open for her desires.

Explore every inch of her body and draw imaginary contours with your fingers and tongue, kiss her neck, breasts, belly and legs, all in a specific order surrounding the most important area and closing in at the same time. All this will increase the tension and when that moment comes both you and her will feel the difference.If all goes well, you might be given the supreme sexual command and that’s “don’t stop!” When you hear that, whatever you do, DON’T STOP!

Making Love is connecting of two people’s souls through two people’s bodies, as one. When there is no stronger way to express your love than sexual Intimacy. Wanting to please each other, make the other happy, share everything, be as close as humanly possible. Making Love is a Sexual and Emotional act. While making love reflects a feeling of affection associated with sexual intercourse. Making love also implies being intimate with your partner, not only physically but also mentally while having sex is just an urge for intercourse. In Making Love Emotions involved, often more pleasurable due to the fact that you are pleasing the person that you love.

While making love is generally referred to intercourse with a partner, spouse or beloved. In simple words, with one you care for or are emotionally attached to. It is an emotional attachment, including infatuation in the beginning of a relationship, is there when making love. It is sharing over all intimacy. Some people also suggest that making love is an expression of love though having sex isn’t because love might not be involved.

One of the most amazing things about being in a seriously loving and committed relationship is the actual art of making love to your partner. It’s going to feel so immensely great that you will want to do it as much and as often as possible. Yes, it’s still a lot of fun to just get physical with someone in the confines of a bedroom. But there’s just a whole new level of enjoyment and pleasure that comes with actually making love to someone. The emotional connection and romance just take it to greater heights.

Making love just really happens to be one of the best feelings in the world. It will enable you to feel more and more connected to the partner you are already so in love with. There really is nothing else in the world quite like it. Having sex may just satisfy one’s sexual urge while making love may please a person’s physical, emotional, sexual and mental urges. It can be said that having sex is merely restricted to a physical act while making love goes to include other urges also.

Sex can be a physical thrill for a night or a few encounters, but lovemaking can be an ecstatic adventure of a lifetime and most women can feel the difference. Sex is a simple physical act, so simple that even animals do it. But lovemaking is a complex expression of LOVE. It’s a desire to communicate the love you have for the other person non-verbally. It gives you a chance to express all the good feelings and thoughts you have about your lover.

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 

 

 

 

 

 
1 Comment

Posted by on June 29, 2019 in Technical

 

Scrum Vs Kanban


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

Article by AXA XL Team…

Which framework works best: Kanban or Scrum? If you are on the verge of a brand new project, I bet this question has posed quite the challenge to your mind. Today Kanban and Scrum have grown in popularity and have taken the place of the previously popular waterfall method.

Agile –  Agile software development is based on an incremental, iterative approach. Instead of in-depth planning at the beginning of the project, Agile methodologies are open to changing requirements over time and encourages constant feedback from the end users. Cross-functional teams work on iterations of a product over a period of time, and this work is organized into a backlog that is prioritized based on business or customer value. The goal of each iteration is to produce a working product.

Scrum – The approach followed here is breaking down a complex task into simpler smaller manageable pieces which are easy to collaborate upon by the respective owners of the scrum.

Kanban – It is a Continuous improvement, flexible process. Kanban helps visualize your work, limit work-in-progress(WIP) and quickly move work from “Doing” to “Done.” It is a framework which utilizes visualization technique, limiting the number of tasks to be taken in “Work in Progress” column.

Scrum Vs Kanban

Kanban and Scrum are both iterative Agile development models, the goal is to get the most important tasks fully done (including testing) as soon as possible. The product should be potentially shippable at the end of the iteration. The difference is with Scrum the end is a set date, with Kanban it could be anytime the features that need releasing are done. In Scrum you plan a fixed period of time and with Kanban you plan just in time.

ks1.jpg

Roles –

  • Scrum is dependent on the scrum owners and is worked upon by them respectively. Scrum has three clearly defined roles.
    1. The product owner advocates for the customer, manages the product backlog, and helps prioritize the work done by the development team.
    2. The scrum master helps the team stay grounded in the scrum principles.
    3. The scrum team chooses the work to be done, delivers increments, and demonstrates collective accountability
  • Kanban is independent of cross-functional team members and parallel roles. The whole team owns the kanban board. Some teams enlist an agile coach but, unlike scrum, there is no single “kanban master” who keeps everything running smoothly. It’s the collective responsibility of the entire team to collaborate on and deliver the tasks on the board.

Release cycle –

  • Scrum makes use of sprints whose duration varies from one week to two weeks. The user stories are then taken up for development, testing and bug fixes. Nowadays, it’s common to have ad-hoc releases in scrum, but it’s long been a best practice to release at the end of each sprint. Teams set an objective for each sprint, the sprint goal, and either approves it for release in the sprint review meeting, or don’t
  • Kanban does not follow any cycle and the process is continuous in nature. In kanban, updates are released whenever they are ready, without a regular schedule or predetermined due dates. In theory, kanban does not prescribe a fixed time to deliver a task. If the task gets completed earlier (or later), it can be released as needed without having to wait for a release milestone like sprint review.

Tracking parameters –

  • Scrum makes use of velocity in planning upcoming sprints taking into account the complexity and number of user stories completed in the previous sprint.
  • Kanban ensures limiting of user stories in “Work in Progress” column to avoid bottlenecks. It tracks the time taken to finish a task from the starting to the end.

The scope of improvement –

  • Scrum does not encourage changes in ongoing sprints.
  • Kanban is open to any changes before the completion of the project. It is flexible in nature.

Fit factor –

  • Scrum is suitable for projects with clearly defined user stories. Acknowledgement on the same by the client for timely completion of the project makes it a fit.
  • Kanban being flexible in nature allows variations in priorities on the basis of the current scenario.

Pick process –

  • Scrum picks the entire batch of user stories from the product backlog for development.
  • Kanban follows the maximum number of tasks allowed in the columns to maintain the sanity of the framework and to avoid bottlenecks.

Delivery –

  • Scrum follows delivery based on sprint planning and prioritize based on the specifications given by the client.
  • Kanban follows the continuous delivery model based on business needs.

Key metrics

  • Scrum – Velocity i.e. the number of story points completed in a sprint—is the central metric for scrum teams. It guides future sprint commitments, or how much work the scrum team takes on in future sprints. If the team completes an average of 35 story points per sprint (Velocity = 35), it won’t agree to a sprint backlog that contains 45 points.
  • Kanban – Lead time and cycle time are important metrics for kanban teams. The deal with the average amount of time that it takes for a task to move from start to finish. Improving cycle times indicates the success of kanban teams.

The above points are easy to remember if you are able to visualize working on them. Ideally where the scrum follows a rather predefined set of principles. Kanban is backed up by the principle of flexibility. It allows you to track tasks that are of utmost importance for delivery.

What Is Kanban? ks3

In order to simplify the manufacturing process and increase efficiency, in the 1940s Toyota implemented just-in-time manufacturing—effectively, making only what is needed, only when it is needed, and only in the amount that is needed.

Kanban is great for teams that have lots of incoming requests that vary in priority and size. Whereas scrum processes require high control over what is in scope, kanban let’s you go with the flow. Let’s take a look at the same five considerations to help you decide. What makes Kanban interesting is this aspect of it – that you could be continuously developing, integrating, testing and releasing at a cadence that you feel comfortable with – and so the whole concept of Continuous Delivery becomes much more ‘natural’ with Kanban.

How Does Kanban Work?

The only essential materials for kanban are a marker, sticky notes, and a board. Create “cards” from the sticky notes representing work items that have to go through several phases, from start to finish. Then draw columns on the board for each phase the cards need to go through, with a number at the top of each column that indicates the maximum number of cards (i.e., work in progress) that can be in that phase at a time. This number probably will and should change as your team improves its ability to gauge and reduce bottlenecks. The columns could simply be labeled “to do,” “doing,” “waiting,” and “done,” or they can be more process-specific, such as in the examples below.

Another helpful thing many teams do is dividing the columns in two, with one lane for “doing” and one for “done,” as you can see in the software development kanban example above. This way, it is clear to whoever is in charge of the following column to know when they can pull another card and begin working on it.

ks 2

The beauty of this system is that it helps you detect where bottlenecks are. The work-in-progress limit stimulates conversations about process problems. In the examples above, you can see some columns are at capacity and some are not, but none has more cards than prescribed.

 

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 

 

 

 

 
1 Comment

Posted by on March 22, 2019 in Technical

 

Tags: , , ,

Root Cause Analysis


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

Article by Karthik.

RCA (Root cause analysis) is a mechanism of analyzing the Incidents/defects, to identify its cause. We brainstorm, read and dig the Incidents/defect to identify whether the defect was due to “testing miss”, “development miss” or was a “requirement or designs miss”. RCA is simply about determining, very specifically, the when, the where, and the why of a problem at its source, before it can ripple out to affect the end-user of an application or website a second time.

Doing the RCA accurately helps to prevent defects in the later releases or phases. If we find, that a defect was due to design miss, we can review the design documents and can take appropriate measures. Similarly, if we find that a defect was due to testing miss, we can review our test cases or metrics, and update it accordingly.

Root Cause Analysis is like a chain of events which go backward, right from the last possible action to the previous and so on, till you reach the start of the problem and the exact point at which it was introduced as a defect. This is called as reverse engineering. There are a few two major questions that we need to ask – WHAT, WHY, WHEN, HOW. With the assistance of these questions, we can dig into each phase of the software life cycle to exactly track the origin of the defect and the point at which it was injected into the system.

Root-Cause-Analysis-Process

Goals: The primary goal of using RCA is to analyze problems or events to identify:

  • What happened
  • How it happened
  • Why it happened…so that
  • Actions for preventing reoccurrence are developed

Benefits: Implementing RCA will help the agency:

  • Identify barriers and the causes of problems, so that permanent solutions can be found.
  • Develop a logical approach to problem-solving, using data that already exists in the agency.
  • Identify current and future needs for organizational improvement.
  • Establish repeatable, step-by-step processes, in which one process can confirm the results of another.

Principles

  • Focusing on corrective measures of root causes is more effective than simply treating the symptoms of a problem or event.
  • RCA is performed most effectively when accomplished through a systematic process with conclusions backed up by evidence.
  • There is usually more than one root cause for a problem or event.
  • The focus of investigation and analysis through problem identification is WHY the event occurred, and not who made the error.

Roots: Root cause analysis is not a one-size-fits-all methodology. There are many different tools, processes, and philosophies of accomplishing RCA. In fact, it was born out of a need to analyze various enterprise activities such as:

  • Accident analysis and occupational safety and health
  • Quality control
  • Efficient business process
  • Engineering and maintenance failure analysis
  • Various systems-based processes, including change management and risk management

Applying RCA: Examples of events where RCA is used to solve problems and provide preventive actions include:

  • Major accidents
  • Everyday incidents
  • Minor near-misses
  • Human errors
  • Maintenance problems
  • Medical mistakes
  • Productivity issues
  • Manufacturing mistakes
  • Environmental releases
  • Risk analysis, risk mapping

Basic method to use

  • Define the problem.
  • Gather information, data and evidence.
  • Identify all issues and events that contributed to the problem.
  • Determine root causes.
  • Identify recommendations for eliminating or mitigating the reoccurrence of problems or events.
  • Implement the identified solutions.

RCA methods

The nature of RCA is to identify all and multiple contributing factors to a problem or event. This is most effectively accomplished through an analysis method. Some methods used in RCA include:

  • The “5-Whys” Analysis” — A simple problem-solving technique that helps users get to the root of the problem quickly. It was made popular in the 1970’s by the Toyota Production System. This strategy involves looking at a problem and asking “why” and “what caused this problem”. Often the answer to the first “why” prompts a second “why” and so on—providing the basis for the “5-why” analysis.
  • Barrier Analysis — Investigation or design method that involves the tracing of pathways by which a target is adversely affected by a hazard, including the identification of any failed or missing countermeasures that could or should have prevented the undesired effect(s).
  • Change Analysis — Looks systematically for possible risk impacts and appropriate risk management strategies in situations where change is occurring. This includes situations in which system configurations are changed, operating practices or policies are revised, new or different activities will be performed, etc.
  • Causal Factor Tree Analysis — An investigation and analysis technique used to record and display, in a logical, tree-structured hierarchy, all the actions and conditions that were necessary and sufficient for a given consequence to have occurred.
  • Failure Mode and Effects Analysis — A “system engineering” process that examines failures in products or processes.
  • Fish-Bone Diagram or Ishikawa Diagram — Derived from the quality management process, it’s an analysis tool that provides a systematic way of looking at effects and the causes that create or contribute to those effects. Because of the function of the fishbone diagram, it may be referred to as a cause-and-effect diagram. The design of the diagram looks much like the skeleton of a fish—hence the designation “fishbone” diagram.
  • Pareto Analysis — A statistical technique in decision making that is used for analysis of selected and a limited number of tasks that produce significant overall effect. The premise is that 80% of problems are produced by a few critical causes (20%).
  • Fault Tree Analysis — The event is placed at the root (top event) of a “tree of logic”. Each situation causing effect is added to the tree as a series of logic expressions.

Based on the results of RCA, you can determine which of the phase has problem areas. For example, if you determine most of the RCA of the defects are due to requirement miss, then you can improve the requirement gathering / understanding phase by introducing more reviews or walk-through sessions.

Similarly, if you find that mostly defects are due to testing miss, you need to improve the testing process. You can introduce metrics like requirement tractability metrics, test coverage metrics or can keep a check on the review process or any other step which you feel would improve the efficiency of the testing. It is the responsibility of the entire team to sit and analyze the defects, and contribute to the product and process improvement.

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 
Leave a comment

Posted by on November 29, 2018 in Technical

 

Tags: , ,

That’s why she’s a slut


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

Article by  Laura Jane Williams..

She’s missing something, and needs you to fill the hole. Literally. Come inside her and stem the flow, patch up the wound with your own body because she cannot do it alone. When he left he took something from her, but she doesn’t know – can’t figure out – what, exactly, it is. So she’ll try anything. She’ll do anything to see what works. She just needs to not feel quite so much.

She’s a slut because it helps. It’s less about the act of fucking you, and more about what it does to her ego to get there. That she can control you. She had no control over him – the way he cried when he said goodbye but said goodbye all the same. She had no control when she got the call about his new girlfriend, second-hand information that made her wonder how long, exactly, it had really been going on. o-SLUT-570

She needed him to be a faithful man so that she could believe faithful men exist, and now they don’t anyone is up for grabs. It is balm for the ego, locking eyes across the bar. Salve for the dented spirit when she approaches. Men love the thrill of the chase, and she loves knowing that she can screw any man she wants if only she’s brave enough to ask. She just needs to make it their idea. She’s in the driving seat of saying just the right amount of provocative. Master of making his pupils dilate in thrilled shock. Will say the unsayable as code for what else she’ll do, too.

She’s not a bad person. She’s not a Madonna, nor is she a total whore. She has friends, and a job, and is liked and respected and popular enough. She commands attention because she’s so in control, so measured, so aware of the cracks she’ll let other people see. Most will be fooled by it. Most will marvel at her confidence and her “go for it” attitude. Concede that she must really have her shit together. But then there will be one or two who linger behind, say less, hold something back because they see it. They see that she’s playing make believe and doesn’t even recognize it herself. They don’t trust it, and they shouldn’t.

She’ll fuck you, and you, and you – one after the other, filling up and filling up but never being filled for long enough. She’ll begin to pride herself on not being like the other girls. Of keeping you at a distance. Ignoring you once you’ve peeled off the condom and flung it in the trash. Because she will always make you wear a condom. She can’t love herself so she sure as hell couldn’t love your child.

She’s a slut because none of you are the answer. As she holds your gaze longer than strictly necessary, rests her hand on your knee a little too high to be friendly, there will be a question in her eyes and in her heart and the moment you lean in to kiss her –tough, and fast, always too fast to mean anything – the tiny speckle of hope that she almost had will be quashed. She’ll just get on with it.

She’ll be wet for you. Turned on as all hell. You might even make her come. But it won’t be from being inside her. It won’t be where she can see you. You’ll slip your hand into her knickers from behind or go down on her in the dark. From there, you could be anybody. Nobody. Him.

She’ll treat you like utter shit and it will make you want more, because the ones who don’t care can be the most attractive when we’re playing the “who is more broken?” game. But you won’t value her. She gave it away too easily, you used each other in a way that can’t be undone. She’ll note your attitude, the way you keep your texts explicit and void of emotion, following her lead, as evidence that all men are the same.

Sexual predators. Easily led. Emotionally stunted.

She won’t feel bad about moving on to the next, because it didn’t mean anything anyway.

That’s why she’s a slut.

Because nobody can disprove her theory. Nobody is saving her from herself. She doesn’t know, yet, that she needs to save herself.

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 
Leave a comment

Posted by on August 14, 2018 in Technical

 

Tags: , , ,

Business Impact Analysis


Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

Article by XLC Team…

A Business Impact Analysis is a process used to determine the effect of an interruption of services on each business unit and the organization as a whole. The analysis can provide information on the short and long term effects of a disaster on such factors as profit, market share and goodwill.

This information in required to develop a business continuity strategy for the entire organization. Please fill out this questionnaire in as much detail as possible. Your input will be valuable in developing an effective Business Continuity program.

A business impact analysis is a key part of the business continuity process that analyzes mission-critical business functions and identifies and quantifies the impact a loss of those functions — e.g., operational, financial — may have on the organization. A business impact analysis (BIA) is critical in assessing the cost of business disruption and how disaster recovery plays a role in mitigating it. The BIA has several crucial elements, which include executive backing; a deep understanding of the organization; and BIA tools, processes and findings.  concept-image-of-business-acronym-bia-business-impact-and-analysis-FGFK4M

Once risks to an organization have been identified — usually through a risk analysis — the next step in a business impact analysis is to determine how the identified risks affect specific business operations. Let’s assume that if all business functions are performing normally, the organization ought to be fully viable, competitive and financially solid. If an incident — internal or external — negatively affects business operations, the organization could be compromised.

Business impact analyses help business continuity/disaster recovery professionals to identify business priorities and validate or modify them for plan development. Questionnaires must be formulated for preinterview data gathering or in-person interviews. People with in-depth knowledge of and experience with the business functions being analyzed are ideal candidates for BIA interviews.

In some cases, it may be possible to develop business impact analysis questionnaires into an automated survey — an example of which is BIA Professional from SunGard Availability Services — in which the results can be captured and summarized. Often, it is useful to include an incident description for interviewees to use when answering the questions. An example of such a situation is when:

  • the business unit’s portion of the building is completely destroyed;
  • all records, data files, technology, supplies and other support systems are lost;
  • some key personnel are not available;
  • primary business processes are affected immediately, and for at least 30 days; and
  • the disaster occurs during a peak processing period for the business unit.

Tips for performing a business impact analysis

Keep in mind the following key tips when performing a business impact analysis:

  1. Get the support of senior management.Given the nature of BIAs, and the time needed for research, be sure to obtain senior management support so that your project goals can be achieved.
  2. Take the business impact analysis process seriously.Although the BIA can take a great deal of time for data gathering and analysis, its value is essential as you develop plans. BIAs do not have to be dozens of pages long; they simply need the right information, and that information should be current and accurate.
  3. There are no formal BIA standards.Despite many business continuity standards being available in the U.S., no formal standards exist for BIAs.
  4. Keep it simple.Gathering the right information is critical; the associated business impact analysis template provides a baseline for information to be gathered. If a one-page business impact analysis summary provides the relevant information, versus one with dozens of pages, it is perfectly acceptable.
  5. Review results with business units.Once the plan is complete, review the findings with business unit leaders to make sure your assumptions are correct.
  6. Be flexible.The suggested template in this article may be too complex for some organizations; feel free to modify it as you see fit to accomplish your goals.
  1. Business unit name: Enter the business unit’s name.
  2. Head count: Enter the number of full-time staff in the business unit and, optionally, part-time staff and contractors, if applicable.
  3. Parent process: Describe the principal activities the unit performs, e.g., sales, contractor interface or investor relationship management.
  4. Priority ranking: Enter a number here for subjective ranking of process importance.
  5. Recovery time objective: Enter a time frame — e.g., one hour, one week — in this section; it describes the time a parent process has to return to business almost as usual following a disruption.
  6. Recovery point objective: Enter a time frame — e.g., one hour, one day — in this section; this is a point in time to which parent process work should be restored following a disruption.
  7. Parent process depends on: Enter names of organizations and processes the parent process depends on for normal operations.
  8. Parent process required by: Enter names of organizations and processes that depend on the parent process for normal operations.
  9. (Optional) Subprocess: Enter a description of supporting activities the unit performs, e.g., sales analysis, financial analysis.
  10. (Optional) Priority ranking: Enter a number here for subjective ranking of subprocesses and their importance to the business unit.
  11. (Optional) Recovery time objective: Enter a time frame; it describes the time a subprocess has to return to business almost as usual following a disruption.
  12. (Optional) Recovery point objective: Enter a time frame; this is a point in time to which subprocess work should be restored following a disruption.
  13. (Optional) Subprocess depends on: Enter names of organizations and processes the subprocess depends on for normal operations.
  14. (Optional) Subprocess required by: Enter names of organizations and processes that depend on the subprocess for normal operations.
  15. Quantitative impact: Enter a financial amount associated with the parent process, e.g., annual revenue generated by the process.
  16. Qualitative impact: Enter a nonfinancial impact to the company, e.g., loss of reputation, loss of customers associated with parent process.
  17. Time needed to recover staff: Enter the number of staff that need to be back to business almost as usual within specific time frames.
  18. Recovery strategy: Enter specific actions the business unit can take to recover to a business almost as usual state, e.g., work from home, relocate to an alternate area, recover to a hot site.
  19. Technology and services recovery time: Enter the system and services in each time frame that must be recovered within the specific time frame.
  20. Comments: Self-explanatory.

An excellent way to learn about a business is to conduct a business impact analysis. In addition to identifying recovery priorities and time frames, conducting a BIA can also identify opportunities for process improvement.

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 
Leave a comment

Posted by on February 22, 2018 in Technical

 

Tags: , ,

What is DevOps? Role of QA in DevOps


 

Each minute of our life is a lesson but most of us fail to read it. I thought I would just add my daily lessons & the lessons that I learned by seeing the people around here. So it may be useful for you and as memories for me.

Article by V Rana & Vaibhav Choksi..

In most software development organizations, QA is considered a function separate from  development units. Indeed, testers and developers have their own roles and responsibilities to take care of.  However, QA and development teams should sync very closely to achieve common objectives of delivering a single, robust application that functions and behaves as per agreed standards.

When one examines the present drift toward DevOps, it’s quite evident that more and more organizations are implementing this software release model with the intention of enabling automation in software deployment. DevOps affords the framework that allows teams to move forward software on a more frequent basis. The conventional idea of a “software release” dissolves into a uninterrupted cycle of service improvement over time.

What is DevOps?

DevOps-Tools-DevOps-Tutorial-Edureka-1

DevOps is projected as the next higher level of agile software development practice that enables coding and testing to take place simultaneously with timely collaboration and communication amongst all concerned functions/ departments. It provides a framework that enables teams to speed-up software releases and gain faster time-to-market, even while ensuring quality at the same time. Traditional role of QA is to detect bugs, but in DevOps, the key responsibility of QA is to avoid the bugs from occurring in the first place

DevOps encourages development and operations teams to function as one single cohesive unit, focused on delivering business values across the IT value chain. It also helps in release management, delivery and deployment with continuous automation. Here we will discuss how DevOps can be helpful to deliver continuous integration & continuous delivery in QA..

Test automation tools are capable of performing tests, reporting outcomes and comparing results with earlier test runs. Tests carried out with these tools can be run repetitively, at any time of day. Test automation framework is a set of guidelines, coding standards, concepts, processes, practices and more, which provides an execution environment for automation test scripts. It allows the user to develop, execute and report on the automation test scripts in an effective and efficient manner.

Build Verification Test (BVT) is a set of tests run on every new build to verify that build is testable, before it is released to a test team for further testing. These test cases are fundamental functionality test cases that ensure application is stable and can be tested systematically. BVT saves time, cost, resources and efforts for test teams to setup and test a build. Test environment virtualization enables optimization of various simultaneously started processes. It can make testing much easier and efficient by eliminating certain dependencies and bring down the cost of setting one or multiple test environments. It considerably increases IT infrastructure flexibility and the efficiency of hardware usage.

 How implementing DevOps can be useful in QA?

The role of QA in DevOps becomes more of an enabler or gatekeeper that links developers and the operations teams. DevOps is an approach to highlight swift, small, iterative development and deployment of applications. DevOps flawlessly integrates all the three functions – Dev, Ops and QA as a single IT entity that deliver value.

14Tools2Take an example of an ecommerce portal. In its release environment, hourly releases are very common. In such cases, load, stress, and security testing become important. With DevOps approach, faster timely releases can be delivered by eliminating the opportunity for people to make errors. The continuous performance evaluation of the portal helps in improving customer experience.

DevOps helps in creating rapid, reliable and repeatable processes. It also benefits in achieving process improvements throughout the software development life cycle by identifying issues and recommending necessary improvements. With the help of DevOps, testers can leverage best practices in agile testing, continuous integration and test-driven development to accelerate QA processes and reduce cycle time.

What is the role of QA in DevOps?

QA has always been seen as a “gatekeeper” for software deliveries. However, in a DevOps environment, QA is part of the process itself since there are no boundaries between development and operations leading to Agile results unlike a traditional environment where development and operations are separated functions and operations team fixed issues raised by development teams.
In DevOps organizations, QA pushes out new development code to a production environment and DevOps teams provide infrastructure and tools to make the deployment process easier while simultaneously verifying that the changes are functioning as per the requirement.

In a traditional QA focused organizations, quality assurance teams focus on finding bugs while in DevOps organizations, the responsibility of quality assurance is not limited to that but to prevent them from arising in the first place. This approach helps in an environment where there is a need for newer releases every few minutes or hours. Here, manual testing is simply ruled out as an option and test automation has to be deployed.

Hourly releases are very common if we consider the release environment of an eCommerce portal. In this case, load, security and stress testing become critical and DevOps practice can help manage better quality releases since quality is an integral part of DevOps. This helps to identify and fix issues before new code goes live on the portal while checking for performance when it’s live.

DevOps helps achieve continuous improvement throughout the development cycle of a software product as QA teams can simultaneously identify issues in processes and recommend improvements wherever necessary. 

Please feel free to share your story and any lessons you learned, you experienced, you came across in your life in the comments below.

 
Leave a comment

Posted by on November 21, 2017 in Technical

 

Tags: , , ,

 
%d bloggers like this: