Make the most of Agile in economic downturn (September 16,2011)

Posted originally on September 16,2011

“Recession is a dreaded word”, my roommate said, when he returned from work in the evening.

“Yeah, it sure is a bad word, but it can lead to operational efficiency and productivity gains in any Organization, if proper procedures are applied,” I replied.

“You’re talking indirectly about cost cutting which is a result of the recession itself.”

“Well, these terms are linked to the dreaded word, but if you take a look at the graphs of Successful companies like, Toyota, GE, Walmart etc., you would find that those played an important role in their Successes.”

“Ok. How can you say that? My company is in the news lately as reports of potential firing of 5000 employees have grabbed the headlines.”

“Isn’t the same case happened two years ago, if I’m correct?”

“Yes, at that time around 7000 were laid off.”

“Ok, don’t you think something could have been done this time around?” I asked.

“I don’t know. I suppose this would need to be looked upon by CxOs, not a Project Manager like me.”

“I would say the change begins with you. Someone has rightly said, “The spark of a tiny idea can ignite dynamic innovation”. Do you agree?”

My roommate paused and said, “Yes, I do agree, what do you say?”

“Yes, I do see an environment of uncertainty where Clients are facing resource crunch, margin pressure and financial problems and, this demands that the Organizations change the way they work in order to survive and compete in this market. A true paradigm shift is required that would enable an Organization to sail through easily. There is bad news all around. But, cutting costs through layoffs as being seen, is not the way. The Organizations need to look at the current processes and methodologies in place in the system, fine tune and tweak it, adopt Agile methodologies to respond to the constant change, remove waste through Lean and then, they can strive to achieve customer delight. Cutting jobs is just a way to douse the fire but it is ineffective in the long run as people do move, but the existing processes which are the real reason of the mess in an Organization are not changed and leads to a vicious cycle. Cutting staff leads to reduced value to the client, which in turn leads to more revenue pressure and again, you cut costs through lay-offs keeping bureaucracy and existing processes in place.”

“Ok. The Agile Project Manager in you has again started speaking, how can you say the Agile ‘buzzword’ can help here?”

“Agile methods help find and remove waste, focus on value, learn from both successes and failures through reviews and retrospectives, debureaucratize the system by empowering the team, cross-functional training, collaboration and communication improve responsiveness and accountability, iteration and as a result, the Customer feels much in control of the project and the team.”

“Yes, it is a radical approach and, sometimes, an Organization is not ready for it.”

“I don’t believe if any Organization is ready for the economic downturn as well. Incorporating Agile is the best choice for Organizations in crisis. Iterations deliver working versions of the software at regular intervals of, 20-30 days, and this approach helps do better next time allowing everyone (Client and the team) to adapt to changing conditions very quickly. It improves the time to market and in the worst case scenario, if the project is suspended for some reason, the risk is minimized as the client may utilize the “done” increment of the software delivered to him. This type of flexibility is not provided by Waterfall approach.”

“You are talking about development projects, how can agile help in Maintenance/Application Support Projects.”

“Agile methodologies like Kanban or Scrum-ban is the best approach to follow for such projects, the visual-boards, reviews, retrospectives and stand-ups keep issues visible, empowers the team to take decisions and improve accountability and communication with Business teams, work in progress limits help divert the attention towards faulty business processes which need correction.”

“Whoa!” He exclaimed. “I would check if we’ve an agile practitioner in my Company, and see if we can start with something right away.”

“Yes, you should. Make the most of Agile in economic downturn and the results will be for everyone to see.”

35 questions to ask when resolving an issue in a Application Support Project (June 26, 2011)

Posted originally on June 26, 2011

The people who have worked in a Production/Application Support project would agree with me that it takes a great deal of skill to be a good Application Support Personnel. Issues come in almost all type of systems/software and the Application Support team has to ensure that these are resolved according to the various Service Level Agreements/SLAs, minimizing the risk to the users of the application. They have to take into account the Business Criticality and act accordingly. Take the example of an error that occurs in a Financial trading platform during business hours which affect a score of users. The Production/Application Support team has to devise a plan, follow appropriate procedures and try to resolve the issue ASAP or else it can have adverse impact on the revenue itself. Knowing the application/tools help to a certain extent but a proper method needs to be followed to identify the root cause of the issue and resolve it.
Here is a list of 35 questions, that can help a Production/Application Support team to Identify and define the problem and take it towards its resolution. I agree that it may not be a comprehensive list but it can help in gaining a better understanding of the problem in the underlying system, and devise a strategy to fix it. A handout of the questions in pdf format is also attached along with the post and it can serve as a quick reference to any Production/Application Support team.

To download the pdf, click here: 35 Questions

1. What is the problem or error or message encountered by the user?
2. How serious is the problem as seen by the customer? What is the severity?
3. What are the details accompanying the issue?
4. How easy is it to restate the problem?
5. How can I restate the problem?
6. What type of issue is this?
7. Has something changed in the system?
8. What was the customer trying to do when he encountered the issue?
9. When did the customer notice it?
10. Does it happen every time? Is it reproducible?
11. Does it happen for all users?
12. Do I fully understand the issue?
13. What can I do which would help me in gaining a better understanding of the issue?
14. Is there any SLA that needs to be adhered?
15. Who needs to be informed during the problem resolution process?
16. Do I have the required tools that would help in resolving this issue?
17. Who needs to be consulted for its resolution?
18. What is the number of systems/processes surrounding this issue?
19. What is the effect of this issue on upstream/downstream systems?
20. Do I have any initial idea on the problem resolution?
21. What other details that I need for problem resolution?
22. Where should I start?
23. What should I do next?
24. Have I taken a look at all aspects of the given or derived information? What does it suggest?
25. Is there any other way I can solve this problem? If yes, what is that approach? Does it make sense to me?
26. Am I able to break the problem and diagnose each part?
27. Do I need to determine the priority of this issue with Customer, in case, there are other tasks at hand?
28. Am I able to identify each component of the problem? Have I been able to identify the faulty component?
29. Does my resolution make sense to me?
30. Is it a workaround or a complete solution?
31. What do my team members think of this solution?
32. What is the status of testing of the solution?
33. Has customer accepted the solution?
34. Do I need to follow up against any outstanding or arising issue?
35. What are the lessons learned from the problem resolution process?

Please note that you may not necessarily have to refer to these questions in the order shown above, some of these can be skipped or modified as per the situation, but it can provide valuable insights in formulating a plan to solve the problem at hand.

Cleared Salesforce.com Certified Service Cloud Consultant exam (June 16,2011)

Posted originally on June 16,2011

I passed Salesforce.com Certified Service Cloud Consultant exam recently. After reading various reviews that it was too tough in comparison to Certified Consultant, I was wary but proper planning did help in nailing the exam. I would like to thank Jeff Douglas, Ben Prozinski and Jen Bryant who shared their experience through their blogs and/or directly through email. Hats off to you Guys.

Yes, the exam was difficult if you take into account the breadth of the material. But, it was expected as Salesforce.com is moving their training programs and certifications more closer to the real world problems that consultants face daily. If you are seriously preparing for this exam, you may want to sign-up for the trial version of Salesforce.com Service Cloud edition, and get your hands dirty by following the study guide. Apart from that, the following references did help me in the preparation and I do hope that it will help the future aspirants as well.

a. Ebook: Service Cloud for dummies
b. Salesforce specific: Documents under “For Support Professionals” and “Support Administration” at this link
c. Summer’11, Spring’11 and Winter’11 release notes with focus on service cloud and force.com flow
d. Top 10 Call Center Metrics
e. Contact Center
f. KCS
g. ITIL
h. Business Continuity in Cloud
i. Jeff’s blog
j. Ben’s blog

Exam strategy: Be cool, have faith in yourself, trust your instincts and use process of elimination in marking out the wrong answers.

Passed CAPM exam today (May 14,2011)

Posted originally on May 14, 2011

I guess it is about time  I put in my 2 cents of CAPM wisdom. When I  went through a post on  “Lessons Learned” last month on PMHub.net, at that time somewhere deep down, I will post my experience soon. Today, I cleared CAPM and I’m sharing my strategy and “Lessons Learned” in this post in the hope of helping CAPM/PMP aspirants out there.

Lesson 1: So, you’ve decided to appear for CAPM/PMP examination, your application is approved and you’ve a full one year to pick a date. Go set your exam date right away. Whether  you chose a date after 2 or 3 months is entirely your choice, but do pick a date. If you’ve a deadline in front, you’ll strive hard to meet it.

Lesson 2: Make a study plan. If you want to take any formal/prep course, it is your wish but do yourself a favor and start devoting atleast 1-2 hours daily. Pick your books, follow atleast two as it’ll make sure that you don’t miss a concept not present in either of the one. I followed “Head First PMP” and “The PMP exam: How to pass on your first try”. But you may want to go for the books written by “Rita Mulcahy” as well.

Lesson 3: Do study PMBOK guide. I didn’t follow it once and it was a mistake. You may not like it at first go but you can finish “Head First” and then come to this book. When I was giving practice tests, I found that few concepts were missing from the books I followed and they were present in PMBOK.

Lesson 4: If you still don’t want to follow PMBOK, you can go with “Q&A’s for the PMBOK® Guide Fourth Edition by Frank T. Anbari”, it is a book published by PMI and you may want to start testing yourself along with your study plan. I used to mark every incorrect MCQ in a separate notebook, write down the key concepts it is based on and it was my quick refresher on the day before the exam. I reiterate that analyzing all incorrect questions will help you reap rich dividends.

Lesson 5: The basic difference between CAPM & PMP is that the former is 100% PMBOK and the latter is 60-70%. Also, CAPM will grill you on ITTOs much more than PMP. So, you should make effort in understanding ITTOs. I purchased eFlashcards course by Cornelius Fichtner and though I couldn’t go through all flashcards (Read: terrified by their sheer number) but I did make an effort to go through ITTOs flashcards (they total to 167 in his course).

Lesson 6: When you start giving practice tests, try and understand the question at first, map it to the Knowledge Area and think of the answer without looking at the options. It’ll help you in a gaining an edge where speed is concerned. I still remember that I scored 40% in my first practice test but during the course of preparation, I started completing the exam in an hour with decent score of 80%+. Today, in the real exam, I completed it in around 55 minutes.

Lesson 7: I was lucky to get hold of JIMBOK on pmhub.net, they are concise notes from PMBOK guide and I owe one part of my success to them. Search for JIMBOK in “www.pmhub.net”.

Lesson 8: Focus on Quality & Risk Management’s tools and techniques. Make a note of all graphs, EV formulas, CPM etc. Get a good hang of them.

Lesson 9: During the exam you must read each question carefully and make a note of words such as ‘except’ etc. Also if you find absolutes in the answers, weigh other option carefully e.g. if one of the answer choice to a question is “All Processes need to be followed in every project”, take a look at other options as well.  This option is most likely not the answer.

Lesson 10: Do not put a gap in your preparation. Start diligently, don’t lose your focus, nail this exam at fist go.

Though, I appeared for CAPM, but these tips can be taken into consideration for PMP as well. For free sample practice tests, check the section “Most Popular Content” on http://www.deepfriedbrainpmp.com.

Best of luck to all aspirants.

Regards,
Sunish Chabba, CAPM

Automating file watch through cygwin

If you receive daily files to load in your Production ORG & looking forward to automate the file watching to data loader operations, the information given below might help you. If your organization already uses job scheduling tools like AutoSys, it’ll be a cakewalk as one file watcher job and another for file copy/parsing can do the job. Else, you can download CYGWIN, a CLI for Windows and mimics Unix like environment. Through Cygwin, you can run any shell script after downloading appropriate bash/ksh package. A sample script that looks for a file at constant interval is shown below. The destination directory can be the default data loader directory, and invoking data loader through command line will take care of loading this file.

while true; do
cp /src_pathfilename /dest_path/filename && break
sleep 300
done

Key terms defined

Cloud Computing: A plug and play style of computing that provides IT enabled capabilities over Internet to Organizations. Wikipedia defines it as “Cloud computing is Internet-based computing, whereby shared resources, software, and information are provided to computers and other devices on demand, as with the electricity grid.”
Major Cloud service providers are Amazon, Salesforce, Google, VMWare, Microsoft.
Buzzwords: SaaS, PaaS, IaaS, DaaS
Software-as-a-Service (SaaS): Have you ever used CPanel on a Linux hosting plan? It comprises of various customizable Linux apps along with server/db configurations. Prime example is a Joomla (open source CMS) or WordPress (Blogging service) app that can be installed and configured through CPanel using clicks and not code. SaaS is somewhat similar to this. A ‘Pay-as-you-go’ service where a client pays a periodic subscription fee for a software deployed over the Internet. This helps the client in maintaining the focus on the real Business issues and the Infrastructure, regular upgrades are maintained by the third party and are mostly seem less in Nature. Point in case is Salesforce.com applications.
Platform-as-a-Service (PaaS): A complete application stack that includes hardware and software is provided to clients and uses varied licensing models. Examples are Amazon EC2, Force.com, Windows Azure.
Infrastructre-as-a-Service (IaaS): The infrastructure of underlying hardware for an application is provided on a rent basis. It can also be referred as Hardware-as-a-Service.
Database-as-a-Service: Clients uses databases hosted in the cloud on a subscription basis. Amazon Simple DB is an example.

I’ll be back soon!!!

An untoward hacking attempt took this blog site down and I’m working to restore the blog posts. I’ll be back soon.

Update: I’ve started to update this blog with  my old posts. The old links cached in Search Engines won’t work now. Sorry for the inconvenience.