Excel – CUT option disabled/greyed out in Microsoft EXCEL

Admit it, Microsoft Excel is one of Awesome application ever built. Still sometimes like out of nothing it can give you surprises which will leave with a sour taste..

The other day I opened excel, worked on Expense details, Right Click and What!!! The CUT option is Disable or Grey out. Like you kidding me. After a little discomforting moment and little google….. Voilla!! Here is the solution.. Go to the following path.


Sometimes you might not see the ‘appdata’ folder in the window explorer.  In that case just directly go to the path ‘C:\Users\vipin\AppData\Roaming\Microsoft\Excel’

Note: Replace ‘vipin’ in above with with your <username>

Here you will find file Excel15.xlb or Excel14.xlb or Excel12.xlb or similar to this depending upon your Excel version. For me it was Excel15.xlb.

I just renamed this file Excel151.xlb. Just rename it to anything, close any open instance of Excel.. Reopen… and that’s it. DONE.

You now have CUT option back in your life.




SCRUM Ceremonies

Published on 02 June 2018. | Last updated: 03 June 2018. |

Literal Meaning of Ceremony: a formal religious or public occasion, especially one celebrating a particular event, achievement, or anniversary.
Ceremony: I love this word ceremony. Even before you say anything everyone gets an Idea something to celebrate and exactly what it is. Everyone gathers, talk to each other and celebrate their achievements

Ceremony Participants Time Purpose
Sprint 0 Complete SCRUM Team
(Scrum Master, Product Owner, Development Team)
Once at starting. Before Sprint 1

Normally if Need arises normally before start of first Sprint.

a) Set up an initial architecture (development, quality assurance, test environments) so that the team can hit the ground developing on day 1 of sprint 1
b) Identify initial product backlog, so there is a robust backlog to prioritize for sprint 1
c) Schedule required ceremonies
d) Prepare preliminary design that can be used as a foundation for the first stories, but that can be refactored and added to as the project progress.

Note: Sprint 0 is no formal SCRUM ceremony, I have presented it here as many times it is needed to create an Initial Product Backlog and Product Backlog is where SCRUM starts. So make sense to put it at top.

Sprint Backlog Refinement/
Backlog Grooming
Complete SCRUM Team
(Scrum Master, Product Owner, Development Team)
10% of Total Sprint Time. This is Done in Middle or End of the Sprint a) Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team, collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised

Note: Sprint Backlog Refinement/
Backlog Grooming is not a SCRUM Ceremony, but good to understand to capture the flow.

Sprint Planning Meeting Complete SCRUM Team
(Scrum Master, Product Owner, Development Team)
1-2 Hours for each week of Sprint, proportionately shorter for shorter sprints. Sprint Planning meeting is done at the beginning of a sprint. a) Discuss each item with the development team.
b) The group collectively estimates the effort involved.
c) The development team will then make a sprint forecast outlining how much work the team can complete from the product backlog.
d) Also discussion is done on how to achieve the same.
Note: That scope of work chosen by Development then becomes the sprint backlog.
Daily Standup / Daily Scrum Complete SCRUM Team
(Scrum Master, Product Owner, Development Team)
15 Min each day – Typically Morning. Each Development Team member updates on following:
a) What was done yesterday?
b) What will be done today?
c) Any impediments?
d) Scrum of Scrums? (If any)
Note: Stand-up is designed to quickly inform everyone of what’s going on across the team. It’s not a detailed status meeting.
Sprint Review Meeting Complete SCRUM Team
(Scrum Master, Product Owner, Development Team) + Any other stakeholders who are interested in the project success
30-60 minutes. Sprint Review Meeting is done towards the end of the Sprint, Like last week of sprint a) Demonstrate the product to stakeholders and get feedback
b) Inspect, Increment and AdaptNote: a) It’s a time for team to showcase their finished work within this sprint and get immediate feedback.
b) Remember, work should be fully demonstrable and should adhere to Definition of Done (DoD)
Sprint Retrospective Meeting Dev Team, SM 30-60 minutes. Towards the end of the Sprint o milestone, Like last week of sprint a) Product Feedback.
b) Inspect and Adapt Processes.
c) Discussion on What went well, What not went so well, What can be improved.
Sprint Complete SCRUM Team
(Scrum Master, Product Owner, Development Team)
2-4 Weeks Literal Meaning of Sprint: run at full speed over a short distance. In Agile: a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increments are created.

Note: Sprint is not a SCRUM ceremony, but I have mentioned it here so to make rhythm with actual ceremonies.

Product Backlog SM, PO, Dev Team The product backlog is emergent is nature which means it is never considered complete, new features, issues, technical changes keep coming and become part of the Product Backlog. Sprint 0, Sprint Planning and Backlog Grooming are the SCRUM ceremonies where it is actually groomed and discussed with the entire SCRUM team The Product Backlog is an ordered list of everything that might be needed in the final product of the project.
It is managed by the product owner in collaboration with Scrum Master and the team. A backlog of the product is an ever-changing list based on the new features, modifications, findings etc. The aim of grooming is to keep the user stories in a prioritized manner where immediate ones are also properly estimated and ready for consumption in the sprints.Note: Product Back is also not a SCRUM ceremony.

Click here to download a formatted Excel of the above topic: SCRUM_Cermonies

Why Agile/Benefits, Cautions.

Why Agile/Benefits, Cautions.

Hey all, Hope you doing well. So when I take you all with me on my Journey of implementing AGILE/SCRUM, the first obvious question you may ask: Why AGILE?

Of course why, I mean life has been so planned in Waterfall Model, all stages planned, lined up one after another so why do I switch to AGILE?

Waterfall methodology was so planned that’s exactly the greatest weakness. How many times, your projects went exactly the way you listed at requirement stage. You have to have physic powers or be Nostradamus to foresee and list each and every requirement beforehand. Never will that happen. Our projects, requirements change due to many factors, client requirement, market conditions, technological upgrades, competition and lot more.

Benefits of AGILE

1.  Stakeholder Engagement

AGILE provides multiple opportunities for stakeholder and team engagement – before, during, and after each Sprint. By involving the client in every step of the project, there is a high degree of collaboration between the client and project team, providing more opportunities for the team to truly understand the client’s vision. The product owner is always involved, the progress of development has high visibility and flexibility to change is highly important. This implies engagement and customer satisfaction.

2.  Transparency and Increased Project Control

An AGILE approach provides a unique opportunity for clients to be involved throughout the project, from prioritizing features to iteration planning and review sessions to frequent software build containing new features. Daily Sprint Meetings also enable transparency and Project control.

3.  Early and Predictable Delivery

By using time-boxed, fixed schedule Sprints of 1-4 weeks, new features are delivered quickly and frequently, with a high level of predictability. The best thing is Product owner always will choose features with maximum business value early which enables that maximum business values are delivered at an early stage of the project.

4.  Allows for Change

While the team needs to stay focused on delivering an agreed-to subset of the product’s features during each iteration, there is an opportunity to constantly refine and reprioritize the overall product backlog. New or changed backlog items can be planned for the next iteration, providing the opportunity to introduce changes within a few weeks.

5.  Focuses on Business Value

By allowing the client to determine the priority of features, the team understands what’s most important to the client’s business, and can deliver the features that provide the most business value. The Product owner always will choose features with maximum business value early which enables that maximum business values are delivered at an early stage of the project.

6.  Focuses on Users

AGILE commonly uses user stories with business-focused acceptance criteria to define product features. By focusing features on the needs of real users, each feature incrementally delivers value, not just an IT component.

7.  Remove Waste

The things to be done are presented mostly in user stories where actual benefit is mentioned which will be delivered to clients or business by the implementation of the feature. Trust me when you pen down the actual value of any feature you (Product Owner) automatically will not put features which are just on top of your head.

8.  Improves Quality

By breaking down the project into manageable units, the project team can focus on high-quality development, testing, and collaboration. Also, by producing frequent builds and conducting testing and reviews during each iteration, quality is improved by finding and fixing defects quickly and identifying expectation mismatches early.

9.  Reduced risks

AGILE techniques virtually eliminate the chances of absolute project failure. As mentioned earlier there is always a quest to deliver features with most business value at an early stage. 80-20 rules apply here, where 20% of the features provides 80% of business values.
Always having a working product, starting with the very first sprint, so that no AGILE project fails completely.

10. Team Utilization

I have observed that AGILE has given an opportunity to better utilize my team resource. How? Well

  • Firstly I (as SCRUM Master and no Project Manager) don’t have to be a shepherd for my team. I serve them, facilitate them and help them to come out of impediments. They organize themselves choose their work, commit for themselves on efforts (I will cover the AGILE Estimation shortly), help each other
  • Secondly, the entire team is work simultaneously. Coders are not sitting till review is being done, testers are not idle until development is done, everyone is engaged and moving on.

Word of caution: Frankly I can list many more benefits of AGILE, but before you step in for AGILE I have few points which you ponder before doing AGILE.

  • AGILE demands a very high degree of customer involvement, while great for the project, may present problems for some customers who simply may not have the time or interest for this type of active participation. Thus ensure you have this kind of customer involvement.
  • AGILE asks for development team completely dedicated to the project. You can’t park resources on multiple projects as this will call in costly context switching and won’t yield true AGILE benefits.
  • AGILE prefers team at the same location. However, there are a variety of ways to handle this issue, such as webcams, collaboration tools, etc.

BIG QUESTION should you always choose AGILE:

  • Your customer wants you to use the traditional methodology and doesn’t want to hear about Agile. End of discussion if the customer wants to keep him happy. Of Couse, you may take him through benefits but if still adamant, take it easy.
  • Your customer requires neat documentation of each development cycle.
  • Customer (Product Owner) can’t accommodate to indulge with team day to day bases.
  • Your project is not very urgent, too complex or novel. Agile methodology is quite demanding, as we mentioned previously, so there is no need to use it for simple or typical projects.
  • Your team is not self-organizing and lacks professional developers.
Hoping the above helps to choose wisely. Leave your comments and you will surely get answers.

Learn to implement Agile Though SCRUM. I have done and share my journey with you all..

Learning. Well, that never stops. The quest to do more, to dwell and indulge in new horizons is never quenched.  IT world and Project Management, it’s a beast and transformer, isn’t it, changing its shape, size, strategy with each blink of an eye….

As a Project Manager, my quest to implement industry best practices is always on to get the best of my Project and Team.

The last couple of years have been topsy-turvy but all for good. The paradigm shift from my blood oath believes (Waterfall) to AGILE. Hereby I am starting series of Articles where I will take you all through my journey of AGILE Implementation specifically SCRUM.

Starting with some theory (bear with me) and then will sail through how I implemented AGILE (SCRUM).

Till now two articles published

  1. https://vijvipin.wordpress.com/2018/05/21/agile-scrum/
  2. https://vijvipin.wordpress.com/2018/05/24/scrum-roles-and-responsibilities/

Well, today is Friday so no new publish. Just enjoy!!

O that RED, I just love RED.. 🙂

Keep following this space,, Questions, Suggestions, Contradictions, Critics all are welcome. Hit me @vijvipin@gmail.com





SCRUM – Roles and Responsibilities.

Learning to implement SCRUM… Before we dwell on details of same let’s get familiar with some Roles and their responsibilities. AGILE/SCRUM projects have different Roles and Responsibilities than that in the conventional waterfall model. Let understand them all.

If you read about AGILE Manifesto the first value is: Individuals and interactions over processes and tools

So first thing first let’s create the team 🙂 and understand who all we need to bring SCRUM to reality. So following are the Roles and their Responsibilities they execute..

1. Scrum Master: The person who ensures the team keeps to the values and practices of Scrum, sort of like a coach.

  • The Scrum Master is considered to be the top-dog in every organization because companies usually hire them and don’t treat them as permanent employees that is why they are with no authority.
  • It is their duty to remove all the hindrance or obstruction in the way of achieving any goal.
  • It is also their role to enforce scrum ceremonies and processes.
  • They are the ones who commit to goals and deadlines on behalf of the team.

2. Product Owner: He is one of the key stakeholders. Typically, the product owner will be the primary user of the product or at least have a deep understanding of who will. Despite this expertise, the product owner does not get to determine how much work happens in the sprint cycles or alter the goals for that sprint.

  • The product owner is responsible for conveying the vision of the stakeholders to the team.
  • They have the authority to alter the scope.
  • The Product Owners are responsible for the return on investment (ROI) that is why they occupy an authoritative position in the firm.
  • Because they convey the vision of the stakeholders that is why they are the voice of the stakeholders.
  • Not only with the team, but they also communicate with the stakeholders about progress and problems.

3. Scrum Team: Everyone works together to do whatever it takes to complete tasks they’ve all agreed on for a sprint.

  • The Scrum Team is responsible for all the activities that lead them towards their sprint goals.
  • They have to work with the Scrum Master to prioritize the items from the product backlog in the sprint planning.
  • Once committed, it is their responsibility to fulfill the commitment and deliver the agreed results on time with great quality.
  • The Scrum Master is not responsible for keeping his team organized that is they it is the duty of the Scrum Team to get self-organized.
  • They have to be agile in the office and have to attend every standup and other ceremonies.
  • They have to participate in all the meetings despite their nature and have to ensure that all the findings of the meetings are getting practically addressed in the project.

4. Stakeholders: Anyone who is impacted by the project is stakeholders. The impact can be positive and negative both.

  • The Stakeholder has to keep a healthy relationship with the Product Owner in order to share every detail regarding his project.
  • The Stakeholder is responsible for conveying his wishes and concerns to the product owner or else the product owner would not be responsible for his project quality and time duration.
  • The Stakeholder has to provide regular input to queries from the Product Owner.
  • Prioritizing the work effectively with the Product Owner is another job that the Stakeholder has to do to ensure his project development.
  • Keep taking updates or keep giving updates regarding any change in the plans.

In upcoming articles, we will be heavily using the above roles. So I would encourage you to do more google and understand these roles well. You may reach me in case any more details…

Keep Learning..


AGILE/SCRUM… these words almost resonating everywhere around me, lots of reads, lots of words around. I am going nuts, almost freaks me now 🙂

It’s time I dig in my own. I would do a series of multiple posts wherein I would try to cover each and every aspect related to AGILE and Its implementation using SCRUM…

To start with: Let me explain what is the Difference between AGILE and SCRUM. Seen people interchangeably using both of these terms when they are not.

A good analogy would be the difference between a recipe and a diet. A vegetarian diet is a set of methods and practices based on principles and values. A recipe for Vegetarian Pulaoo would be a framework you can use to implement your Vegetarian diet. This is similar to the relationship between Agile (the diet) and Scrum (the recipe you follow).

So the Vegetarian diet plan gives you some basic principles you need to follow to be vegetarian. Keeping those principles in mind you can create countless dishes which are just a way to implement the Vegetarian diet.

Hmmm, tickles your taste buds, right. I will try to keep things very short and crispy. The idea is to just help to get started with AGILE and its implementation through SCRUM.

In the next part of this series, I would publish more on both the terms. I take you through Roles and Responsibilities of SCRUM, which is the backbone to understand before moving any further.. so keep visiting.

Suggestion, questions, need more details: Comment below or mail me: vijvipin@gmail.com

Keep learning…


Manual sorting in pivot table – Excel

Hmm,, well lets see,, how many of you excel lovers have faced a tough time with manual sorting in pivot table. I am sure all,, Yup I admit I am also included 🙂

Well tough times are gone… Just like on following link and life easy. Trust me I tried this myself.. In case anyone still face any issues.

In case you still face issues leave a comment and I will provide one more example..

Manual Sorting in Excel