Monday, September 2, 2019

Hard Work Vs Smart Work - Lets get this settled...


It is something I've been thing for a long long time that I decided today; let me settle this now..

I believe “Smart work” is skill, while hard work is a virtue. I’m not advocating for being dumb here - working hard doesn’t mean not using brains.
Both are important. However, hard work is more fundamental.
This is because, it is more inclusive than smart work - meaning, anyone can offer hard work and commitment - irrespective of their IQ or talent. That is why hard work is always regarded higher, though “smart work” looks more glamorous.
“smartness” can be context based and varies case to case. I may be skilled at something and can find smarter ways of accomplishing things in that area of skill. For e.g., a smart advocate may not necessarily be smart at using her laptop. However, she can work hard to gain skills so that she becomes smart at it. Yes, I hear what you are saying… she may smartly hire a PA who can help. Again, this way, she can free up her time to work hard at helping her clients - so that she becomes a “great” advocate - so that she can taste excellence!
The one thing I hate is people thinking that by being “smart”, one need not work hard. That is wrong and may eventually be disastrous. In a team, I’d rather consider a person who can work hard but may not be very smart against a “smart” who doesn’t want to work hard - because, he can be guided. But a so called smart who is not ready to work hard is a disaster in the team!
Hard work and Smart work are not mutually exclusive and no matter how smart you are, you cannot be your best unless you work hard. So I think hard work along with a good application of brain is a must have for excellence.
Smart work is skill, hard work is WILL!


Simply Yours,
Ramkumar NJ

Wednesday, May 18, 2016

Agile Myths - Busted!


One of my colleagues - a good agile coach - once told me, "Agile is one of the most abused words in the industry". I couldn’t agree more! While agility strives for welcoming change in requirements, quick adaption to change, eliminating wasteful processes, empowering developers, it is not intended in doing things at random. I have however seen people saying this in the name of "Agile" and hence this article, in an attempt to bust some of these myths.

Myth1: Agile means Ad-hoc

People think this way because the initial project plan is not "detailed" and is not written on stone. However, it doesn’t mean there is no planning. Planning in agile happens in multiple waves - called the rolling wave plan at multiple points of the project based on the available inputs at that point. This helps creating realistic plans rather than creating a plan that is not even looked into during execution or a plan that, if followed, leads to product's failure.

Myth2: Agile is undisciplined

Agile liberates you from constraints/processes that are followed at the cost of adding value to the project. But to create value, it mandates a strict discipline to be followed - else speed up for a failure. For e.g., In SCRUM, developers can choose to pull whichever user story they like to develop. However, you are mandated to discuss this in the daily stand-up meetings so that everyone in the team is aware and the dependencies are thought through. It mandates that anything and everything developed needs to come from the product owner as user story in the product backlog. It mandates that you need to have a sprint planning to decide the sprint goals and the stories to be developed. It mandates you cannot change stories picked up for a sprint in the middle of the sprint, unless if the sky falls. It mandates burn-down charts and task boards speak the truth at any given point in the sprint. It mandates that you have a sprint review at the end of each sprint with the stakeholders. It mandates a sprint retrospective at the end of each sprint. Above all, it mandates Trust and Transparency. This is Agile discipline and there is no compromise

Myth3: Change in Requirement with no trade-off

One of the key principles of Agile is to welcome change. This is often misunderstood that you can change anything anytime with no trade-off - very unrealistic! The traditional models have a detailed plan to strictly follow. So it automatically discourages change. This is because you have planned everything with a set of requirements and changing that needs a costlier change in plan and reworking. In agile, since the methodology by itself is built for changing requirements and development is done on iterative increments, it is much more accommodative to change. However, depending on the change, the priority of some other stories may be lowered and pushed to later iterations, some stories may be removed to hit the release date or more iterations may be needed to complete all stories. The product owners and customers should understand this. Agile can handle change with relative ease and help creating products that ultimately serve the business needs instead of a product that gets built on-time and on-budget but never gets used. Forget Agile, no methodology in this world, can predict a fixed date and fixed budget for changing/evolving requirements and additional scope.

Myth 4: No documentation

Agile gets rid of unnecessary documentation that are created for the sake of following "the process". For e.g., there is no need of filling in elaborate forms for record purposes; there is no need to minute every other meeting to create "evidence" - Trust is an undisputed trait of Agile teams; you need not create the system first in paper in the name of “design" or "TDD" with all the pseudo-code (sometimes even the code!!) before hitting the actual code. But you definitely have to create/update documents needed for successful development and tracking - for e.g., backlogs, progress radiators like burn-down chart, task board are very essential to build neat systems.

Myth 5: Agile means no control

A cheetah is agile yet in complete control - watch it in action! Agile projects are not any different. The methodology gives you ample techniques to stay in complete control throughout the execution. For e.g., during every iteration you demonstrate the product to the customer/product owner. This gives them the control over the product being built and ensure it caters to the changing business needs. The development team has complete control over their activities during a sprint - no one can disturb them in the middle of a sprint. The product is continuously and rigorously tested giving absolute control over the quality of code. This gives multi-dimensional control rather than single string control.

Myth 6: Agile team is a robot with no downtime

Yes, Agile strives for delivering value to customer at a quicker pace. But it also believes in sustainability over a long period. Delivering at constant pace is one of the agile principles. So, the team needs to be both passionate and balanced. A high stress on the team could challenge both quality and sustainability. Some of the frameworks like extreme programming(XP) recommends work not more than 40 hrs a week to maintain a good balance and productivity. There are even teams that gives a forced day off to recharge if a team member works beyond prescribed hours.

Myth 7: Agile is a "Silver Bullet"

I'm sure by now this myth is busted! While Agile is highly tuned to deliver value early, it doesn't substitute skills or reduce the complexity of a given problem. Agile teams can also fail but the good part is they quickly learn from failure and adapt/adopt the learning immediately instead of waiting for the next project. Agile, for sure, offers a structured way to handle project with high degree complexity & uncertainty in a much optimized fashion.


Now that I’ve given my thoughts, it is your turn to add yours…

Simply Yours,
Ram

Wednesday, August 12, 2015

"Consumerization" - continued..

So, we were talking of consumerization...

There used to be a time when a email-id like yourname@yourdomain.com would mean hosting a mail server, purchasing, deploying and maintaining licensed software.. now its all history! yourname@yourdomain is available at a click of a button - from your smartphone - costing less than Rs.150 per month per user. No buying hardware/software, no complexity - just pay and use. 

A recruiter with a long list of urgent job requisitions to fulfill, on her way to office, checks out the candidate profiles from a mobile app that integrates job sites like naukri/monster and social media like LinkedIn. To her surprise, the app not only provides the candidates, but intelligently suggests who is the best fit! Soical Analytics!!

You are not at your desk and your team member has an issue.. he picks up his phone, takes a picture of the screen and sends you a whatsapp. You look at the screenshot and provide a solution - issue resolved in a min! The solution can immediately be posted in your company's social website to help the whole group when faced with similar issue - collaboration!

Extending it further, the CEO of an organization can now look at the business projections for the next two quarters from his tab or mobile while waiting near the boarding gate... and takes key decisions on the fly!

...looks simple but there is a lot of tech horse power galloping in the background to digest data from multiple systems and deliver the juice - with minimal investment on hardware or software.. (now dont tell me that you still need to buy a device, that is covered in the minimal investment)

Forget all that, how often are we now forced to stop our car to ask for route - google guru navigates you!

And tomorrow, not very far, when you drive into a mall, your mobile will beep with the offers that you will be interested in.. guide you to the exact place where you will get what you want, remind you to buy the multivitamin when you pass through the shop that sells it and suggest you the restaurant based on who is with you in the car!! 

All these "high-tech" will be accessible to everyone, thanks consumerization and its mom, Digital!!


Simply Yours,
Ram

Friday, July 24, 2015

"Consumerization" - What the heck does it mean in IT?





Pretty old topic for the gurus, maybe. But it is more relevant today!

Consumerization in/of IT has begun already and it has started transformation of the whole field and its impact on a common man. I was in a meeting today, where one of the discussion was about "What is consumerization". It was there, I understood that there is a mist that prevails even amongst experienced, that needs to be demystified. Hence this article!

Firstly, let us forget "IT". What do we do as a consumer? pretty simple... we consume and we pay for what we consume - simple and straight!

What do you consume - Electricity/Gas (Utility), cable TV, Internet, etc, etc. But can IT be consumed like this? This is the crux of consumerization.

Now translate this to IT... can we?

There was period when people "Bought" and "Owned" software licenses for a period - no matter which small part of the software they used and how long they used it within the period prescribed.

There was a period when people "Bought" and "Owned" hardware - you had no choice. If you wanted to do an experiment for a month on a solution before deciding if the solution really works, you still had to buy the infra!

But today....

If you want, lets say a system with 512 GB RAM and a 2 TB harddisk, for a month - you can just get it by a simple subscription - the moment you are done, you can unsubscribe.

Similarly, if you need a HCM system for a 50 employees' firm, you can just subscribe to a SaaS application without worrying about the infra or the software license. You have it as long as you need it through subscription.

Thus consumerization is the philosophy of bringing down IT from the mountains to plains, if I can say so. It becomes reachable to anyone, whether you are a startup or a Fortune 500. That is what you call "consumerization"

This philosophy is made a reality by application of technology - Cloud, Social, Mobility!

I think I've made a descent attempt in demystifying. If not, wait for my next post :-)

Simply Yours,
Ram