Office life experience (Year 2014 to May 2019)
My office life was changed with the
posting in new office at Data Centre. I was given a new assignment of
handling new responsibility with new project with as many as 50 members to
assist in dealing with new software and software engineers. It was the day
in July 2011, when may old bosses believe in my calibre and technical
capability to handle the project. The project was consolidation of
international product softwires including Rating, Convergent billing, CRM,
Clarity, Formatting, FRCS, Accounting and Finance.
Joining the job after transfer from old
office was a wonderful experience. You get to learn a lot of new things, a lot
of knowledge about work, new people, etc. You might have tired of
working culture and stress in the old office.
Speaking of me, life has changed beyond
what I imagined. Not only was this a massive change, but somewhat jarring as I
joined my office shortly after relieve order from old office.
==
Joining a new office at Data Center,
Pune, after being relieved from your previous one Jalna City can be an
emotional and transformative experience. TDM Jalna in-charge, told me that you
could be relieved only after a proper substitute is posted in your place. It was painful to hear the wordings that
despite working with devotions and honestly on the post, I could get the reply
was unexpected.
Luckily, the PGM Finance Circle office came to visit,
Auranbad SSA for office work and my friend told me to take the advantage of CHQ
in-charge and discuss about your transfer order, as I had already completed a
tenure period of more than 3 years. I
remember the day I came to Auranbad SSA to met PGM F in Transit quarter,
travelling from Jalna City. Initially,
he shown reluctance to deal with the office matters at far away place, but he
was a good and decent superior, he permitted to met all those waiting for
transfer orders.
Sometimes, typically happens during
such a transition period are as follows:
1. Initial Adjustment
a) Relieve order with
substitute for posting at the station.
b)
Orientation: You're introduced to the company's
policies, culture, and your team. It's a chance to learn about the new
workplace environment.
c)
First Impressions: Meeting new colleagues and
managers can be exciting and signing the charge over report with indications
what are the important items made over by the reliever.
2. Learning Curve
a)
Understanding New Systems: Adapting to the tools,
workflows, and expectations of your new role.
b)
Exploring the Culture: Getting used to the
unwritten rules, office etiquette, and team dynamics.
c)
Arranging shifting of the house hold items from old
city to new city.
3. Reflection on the Change
a)
Comparisons: You might compare the new environment
with your previous workplace, identifying differences in management, workload,
or work-life balance.
b)
Relief and Excitement: A sense of closure from the
old job and excitement for the opportunities ahead.
4. Integration and Growth
a)
Building Relationships: Forming bonds with
colleagues helps you feel part of the team.
b)
Proving Yourself: Demonstrating your skills and
learning how to contribute to the company's goals.
5. Handing over the Staff and pending items to
be completed by the new joinee.
==
My feelings about new office was, If
you are surrounded by your good subordinates and descent work culture, then you
can call yourself to be the luckiest. Of course, it has some indecent office
collogue and other staff dirty, filthy rude
nature.
Dealing with an indecent dirty
colleague in the office can be challenging, but it's important to handle the
situation professionally and assertively. The following are the points as to how
you can manage such situations effectively:
---
1. Identify the Behavior
a. Assess the Situation: Determine what makes the
colleague's behavior inappropriate (e.g., unprofessional comments, rude
actions, harassment, or disregard for boundaries).
b. Avoid Overreacting Initially: Sometimes, actions
might come off as inappropriate due to miscommunication. Ensure you're
perceiving the behavior clearly. ---
2. Set Boundaries
a. Be Assertive: Politely but firmly let the person
know their behavior is unacceptable. For example:
b. "I feel uncomfortable when you make such
comments. Please stop."
c. Stay Professional: Avoid reacting emotionally;
remain calm and composed.
---
3. Document Incidents
a.
Maintain a Record: Note the date, time, and nature
of each incident. This can be helpful if the behavior persists and needs to be
reported.
b.
Include Witnesses: If others observe the
inappropriate behavior, it strengthens your case.
---
4. Engage HR or Management
a.
Report the Issue: If the behavior continues, inform
your supervisor or HR department. Provide clear, factual information and
evidence.
b.
Follow the Procedure: Companies often have policies
and grievance procedures in place for handling such matters.
---
5. Maintain Distance
a.
Limit Interaction: If possible, avoid unnecessary
contact with the person while maintaining professionalism.
b.
Focus on Work: Prioritize your tasks and avoid
letting the behavior affect your productivity or morale.
---
6. Seek Support
a.
Talk to Trusted Colleagues: Share your experience
with someone trustworthy for advice or support.
b.
Professional Help: If the situation causes
significant stress, consider counseling or seeking external advice.
Standing up against indecent behavior
not only protects you but also contributes to a healthier workplace for
everyone. Have you faced such a situation? If so, how did you handle it?
==
On joining new office at Data Center, I
was posted in the office, as per my choice as my bosses were very much respected
me and always took care of my postings and knowing my
technical caliber, ability, appetency , capability , dignity, for
worked since the time of data migration from NIC to C-DAC, C-DAC to CSMS
developed by renowned MNS, from CSMS to CDR system, Call Detail Records
(CDR) based Customer Care and Convergent Billing system to consolidate billing
centers and migrate from meter based billing, licensed by the multiple overseas
Software companies.
I remembered the day when Director Finance came from CHQ New Delhi to our office, after few month of my joining new office, for meeting with Project Circle in-charges in the Conference hall. The meeting was scheduled early morning and I was little bit late for coming to office meeting. I entered into the Conference hall, with the permission and sat on the available chair in the meeting. The meeting was on-going with discussion as per Agenda and all were busy in discussion. To my surprise, Director Finance stood up saying excuse me and came to me to shake hand and say hi. I was proud of him that a person on topmost post, can react. When the **topmost boss shows you respect**, it’s a moment of pride and a reflection of your contributions and character. This positive interaction can boost your morale and set the tone for a healthy and motivating work environment. Here’s how to navigate such a situation effectively.
When the topmost boss shows you
respect, it’s a moment of pride and a reflection of your contributions and
character. This positive interaction can boost your morale and set the tone for
a healthy and motivating work environment. Here’s how to navigate such a
situation effectively:
1. Acknowledge Their Respect
a. Respond Graciously: Show gratitude for their
recognition, whether it's through words or actions.
b. Example: "Thank you, it means a lot to hear
this from you."
c. Stay Humble: A respectful boss appreciates team
players. Avoid letting the recognition inflate your ego.
2. Build a Stronger Rapport
a.
Engage Positively: Use the opportunity to establish
a good working relationship with them. Share your ideas or ask for guidance on
improving your role.
b.
Understand Their Leadership Style: Observing how
they lead with respect can help you align with their expectations.
3. Leverage the Opportunity
a. Enhance Your Confidence: Knowing that your top boss
respects you can empower you to take on challenges or responsibilities with
renewed enthusiasm.
b. Contribute More: Their respect likely stems from
your work ethic or attitude, so continue performing well to reinforce their
trust.
---
4. Be a Role Model
a. Pay It Forward: Treat your colleagues and
subordinates with the same respect. This fosters a culture of mutual respect in
the workplace.
b. Maintain Professionalism: While respect from a
senior leader is significant, ensure your actions reflect the trust they've
shown.
---
5. Understand the Implications
a. Recognition of Value: It could mean that your work
is making a tangible difference.
b. Potential Growth: Respect from the top boss might
open doors to new opportunities, such as leadership roles or projects.
===
Taking on a new project in telecom
billing and collaborating with IT engineers to implement software changes can
indeed be a challenging yet rewarding experience. Here's how such a situation
typically unfolds and how you can navigate it effectively:
---
1. Understanding the Challenge
a. Complex Requirements: Telecom billing systems are
intricate, involving customer management, call detail records, payment
processing, and compliance with regulations.
b. Coordination with IT: Engineers may have their own
priorities or technical constraints that can slow down progress.
c. Change Management: Modifying existing systems can
be risky, with potential impacts on performance, security, and data
integrity.
---
2. Steps to Manage the Challenge
# a. Clear Communication
a. Define Requirements Clearly: Work with stakeholders
to document the exact changes needed. Use diagrams, flowcharts, or case studies
to make the requirements explicit.
b. Bridge the Gap: Translate business needs into
technical terms IT engineers can understand. Similarly, communicate technical
constraints to business teams.
# b. Establish Collaboration
a. Workshops and Meetings: Organize sessions between
IT, business teams, and vendors to align on goals and timelines.
b. Agile Approach: Break the project into smaller
tasks with frequent checkpoints to ensure alignment and progress.
# c. Understand IT Engineer's
Perspective:
Technical Feasibility: Some changes
might require substantial rework or upgrades. Collaborate to prioritize changes
that have the highest impact with minimal disruption. Resource Allocation:
Ensure they have the time, tools, and support needed for the changes.
---
3. Overcoming Specific Challenges
Resistance to Change: Engage engineers
early in the project to get their buy-in. Show them how the changes benefit the
organization and their work. System Downtime Risks: Plan changes
during low-traffic periods and ensure a rollback plan is in place if issues
arise. Testing: Conduct thorough testing in a sandbox environment
to identify bugs or performance bottlenecks before deployment.
---
4. Project Management Tips
Set Realistic Deadlines: Work with IT
engineers to create a timeline that accommodates both technical challenges and
business needs. Track Progress: Use tools like JIRA, Trello,
or Microsoft Project to monitor tasks and dependencies. Escalate
When Necessary: If delays occur, involve senior management to resolve resource
or prioritization conflicts.
---
5. Celebrate Success
Once the software changes are
implemented, recognize the IT team's efforts alongside the business
team. Document lessons learned to make future projects
smoother.
Navigating such a project requires
patience, technical understanding, and excellent communication. How did you tackle
the challenges in your telecom billing project? Were there specific hurdles you
faced with the IT team?
====
Dealing with a politically motivated
and habitually delaying
team leader in an IT company can create frustration and disrupt project
timelines. This kind of behavior may affect team morale and productivity if not
addressed properly. Here’s how to handle such a situation professionally:
1. Understand Their Behavior
a. Political Motivation:
They may prioritize their personal gains or alliances over the team’s
objectives.
b.
Habitual Delays: Procrastination might stem from
poor time management, lack of accountability, or an intentional tactic to
control outcomes.
2. Focus on Professionalism
a. Stick to Facts: Avoid engaging in their political
games. Focus on the project goals and facts rather than opinions or
biases. Be Transparent: Document communications and ensure
transparency in your work to avoid misunderstandings or blame-shifting.
3. Proactively Manage Delays
b. Follow Up Regularly:
Politely but persistently remind them of pending tasks and deadlines. Use
emails or formal communication for tracking.
c. Escalate Through Channels: If their delays
significantly impact the project, raise the issue with higher management or HR,
providing evidence of the impact on productivity.
4. Minimize Dependency
a. Collaborate With Peers: Work closely with team
members to find alternative solutions or divide tasks in ways that reduce
dependence on the leader. Take Initiative: If appropriate, take on
leadership for specific tasks or responsibilities to ensure progress.
5. Build Alliances Wisely
b. Avoid Drama: Steer clear of office politics while
maintaining professional relationships with all team members. Find
Mentors: Seek guidance from senior colleagues or mentors who can offer advice
on navigating the situation.
6. Document Everything
c. Keep Records:
Maintain detailed records of assigned tasks, deadlines, and communications.
This protects you in case of blameshifting or disputes.
d. Performance Impact: Document how their delays
affect the team’s performance or project delivery to present a strong case if
needed.
7. Use Conflict Resolution
Tactics
a. Private Discussions:
If feasible, have a candid conversation with the leader. Politely express how
their actions impact the team and suggest improvements.
b. Mediator Involvement: If direct communication
doesn’t work, involve a neutral senior manager to mediate.
8. Focus on Personal Growth
a. Learn From the
Experience: Observe and avoid adopting negative traits in your own leadership
or work style.
b.
Look for Opportunities: If the situation persists
and becomes toxic, consider exploring opportunities within the company or
elsewhere where merit and professionalism are valued.
===
Payment System :
|
1. Configure Reference
Data |
|
|
1. Collection
Channel…………………………………………………………………………………………………….5 |
|
|
2. Product
Details………………………………………………………………………………………………………….5 |
|
|
3. Currency
Types……………………………………………………………………………………………………….5,6 |
|
|
4. Currency
Conversion Rate…………………………………………………………………………………….…..6 |
|
|
5.
Bank……………………………………………………………………………………………………………………..……6 |
|
|
6. Credit Card
Types………………………………………………………………………………………….….….…6,7 |
|
|
7. Collection
Counter………………………………………………………………………………………….….….….7 |
|
|
8. Collection
Desk (Bank) ………………………………………………………………………………….….……….7 |
|
|
9. Collection
Desk (Post Office)………………………………………………………………….….…..………7,8 |
|
|
10. Collection
Desk (Kiosk) ……………………………………………………………………………….……..……8 |
|
|
11. Collection
Desk (E-Seva)……………………………………………………………………………..…………..8 |
|
|
12. Collection
Desk (Franchisee)…………………………………………………………….……….…………….9 |
|
|
13. Collection
Desk (Bill Desk)………………………………………………………….…………………….………9 |
|
|
14. Collection
Desk (IVRS) ………………………………………………………….………………………………….9 |
|
|
15. Collection
Desk (ECS) ……………………………………………………………………………….…………9,10 |
|
|
16. Credit
Banks……………………………………………………………………………………………………………10 |
|
|
2. Counter
Payments |
|
|
1. Single
Payment……………………………………………………………………………………………….……….10 |
|
|
2. Multiple
Payments………………………………………………………………………………………….……….11 |
|
|
3. Deposit
Payment…………………………………………………………………………………………….……….11 |
|
|
3. Point of
Sale…………………………………………………………………………………………………………………….……11 |
|
|
4. Cancellation
of Payments |
|
|
1.
Cancellation………………………………………………………………………………………………….…….……11 |
|
|
2.
Transfer……………………………………………………………………………………………………………….…..11 |
|
|
5. Reversal of
Payments |
|
|
1.
Reversal……………………………………………………………………………………………………………………11 |
|
|
2.
Transfer…………………………………………………………………………………………………………………...11 |
|
|
6. Batch
Reconciliation…………………………………………………………………………………………………………..…11 |
|
|
7. Generate Daily
List…………………………………………………………………………………………………………….….12 |
|
|
8. Generate
Challan……………………………………………………………………………………………………………….…12 |
|
|
9. Enter Scroll
Report………………………………………………………………………………………………………………..12 |
|
|
10. TR
Reconciliation……………………………………………………………………………………………………..…….……12 |
|
|
11. Counter
Close………………………………………………………………………………………………………………….….12 |
|
|
12. View Counter
Status…………………………………………………………………………………………………..………12 |
|
|
13. View Batch
Status…………………………………………………………………………………………………….………..12 |
|
|
14. View Payment
Details………………………………………………………………………………………………………..12 |
|
|
15. Receipt
Reprint…………………………………………………………………………………………………………….…….12 |
|
|
16. Receipt for
Dealers……………………………………………………………………………………………………….…….12 |
|
|
17 File Structure |
|
|
1.
Add………………………………………………………………………………………………………………….………12 |
|
|
2. Modify/
View………………………………………………………………………………………………………….13 |
|
|
18. Upload
Batch………………………………………………………………………………………………………………………13 |
|
|
19. View Offline
Errors……………………………………………………………………………………………………………..13 |
|
|
20. Offline
Payments |
|
|
1. Add Payment
Batch…………………………………………………………………………………………..…….13 |
|
|
2. View/Modify
Payment Batch…………………………………………………………………………….……13 |
|
|
3. Post
Batch…………………………………………………………………………………………………………….…13 |
|
|
21. Schedules |
|
|
1.
Add…………………………………………………………………………………………………………………………13 |
|
|
2. Modify/ View/
Delete…………………………………………………………………………………………….13 |
|
|
3. Add ECS
Schedule……………………………………………………………………………………………………13 |
|
|
4. Modify/View
ECS Schedule………………………………………………………………………………….13 |
|
|
22. Reports |
|
|
1. Bank
Reconciliation Report……………………………………………………………………………….…14 |
|
|
2. Print
Challan……………………………………………………………………………………………………..…14 |
|
|
3. Commission
Report…………………………………………………………………………………………….14 |
|
|
4. Product Sold
Report…………………………………………………………………………………………...14 |
|
|
5. Unvouchered
Amount Report…………………………………………………………………………….14 |
|
|
6. Desk
Collection Report…………………………………………………………………………………….....14 |
|
|
7. Consolidated
Collection Report………………………………………………………………………..…14 |
|
|
8. Missing
Schedule Report……………………………………………………………………………….…….14 |
|
|
9. Counter
Payment Count Report……………………………………………………………………….…14 |
|
|
10. Receipt
Reprint Report…………………………………………………………………………………….…14 |
|
|
11. Payment File
Error Report……………………………………………………………………………….…14 |
|
|
12. Batch-wise
Payments Report…………………………………………………………………… |
|
===
Learning from a bad boss can be as
valuable as working for a great one, as it often highlights behaviors to avoid
in leadership. Here's an example:
What I Learned from a Worst Boss
The worst boss I had was overly
controlling and dismissive of employee input. They micromanaged every task,
which stifled creativity and made the team feel undervalued. This experience
taught me:
- The
Importance of Trust: Empowering team members by trusting their abilities boosts morale
and productivity.
- Value
of Communication:
Dismissing feedback leads to resentment and missed opportunities for
improvement.
- Need
for Respect:
Respect and acknowledgment of others' contributions create a positive,
collaborative environment.
Ultimately, this boss showed me how
critical it is to be approachable, foster teamwork, and build mutual respect in
leadership roles.
What I Learned from a
Great Boss
Working under an exceptional boss is an
inspiring experience that provides invaluable lessons. Here's what I learned:
1. The
Power of Empowerment
My best boss trusted the team to take ownership of projects and make decisions.
This taught me the importance of empowering others, which builds confidence and
drives innovation.
2. The
Value of Clear Communication
They were transparent about goals and expectations, which created alignment and
eliminated confusion. I learned that clarity fosters efficiency and
accountability.
3. The
Importance of Empathy
They genuinely cared about our well-being and challenges, offering support when
needed. This showed me that empathy strengthens loyalty and morale in any
workplace.
4. Lead
by Example
My boss demonstrated dedication, integrity, and a strong work ethic, inspiring
the team to do the same. I realized that leading by example is key to earning
respect and trust.
5. Encourage
Growth
They prioritized mentorship and provided opportunities for professional development.
I learned that investing in people’s growth benefits both individuals and the
organization.
These lessons not only shaped my
professional approach but also influenced my personal values.
In my office life, I had moreover
learnt more good things from good bosses than bad bosses. The bad bosses have done the following in
carrier life :
1. Bad bosses
damaged my carrier life, by making adverse remarks in the personal service book
or play a blame game, by way of complaining to the head office.
2. Broken
my heart selfishly, rather recommending the rewards for others for
nothing. A bad boss who plays favouritism or act unprofessionally while
granting award for good performance to other employees
3. Bad
bosses are always trying to catch me making mistakes to make a case for letting
you go or to make out in public.
4. Bad
bosses are often deliberately try to demoralize the work culture, either
through passing wrong comments, undermining their work, or taking credit to
himself for the work done by me.
5. Bad bosses
are often having a bad temper. They get easily frustrated or angry on small
mistake or blame the employees for mistake by himself
6. Bad bosses behave
with their employees in such way that they feel whether to laugh or to cry.
7. Bad bosses
always plan to suck the blood out of you. Some bosses spread negativity among
their employees by saying this. They say this so that the employees work more
because it is not in their power to guide or motivate the employees for better
work
8. Bad bosses
accept deficiency, mediocrity rather than coaching and criticise the team for
more Excellency
9. Bad
bosses can be more damaging to your soul than you think. They are of prejudicial mind while
appreciating the good work.. They are white collared snakes in
suits.
10. Bad bosses makes your work difficult to do your job
efficiently, so
as to punish you for
poor work.
11. Bad bosses used to take pleasure in making others cry and he start smiling
to see others crying.
12. bad bosses
carry inflated ego that if you surpass him and talk to his next bosses, then
he became snake in the suit. Such bad
bosses don’t like his employees reporting his bosses as they feel it
insubordinations.
13. The bad
bosses prefer to hear an abusive language in the talk of their employees or
uncomfortable work environment for others.
14.The bad bosses
follow their technique of favorism to their employees in their good book and
creates a negative work environments, by not inviting you for office discussion,
rather inviting other co-workers.
15. Bad bosses
lack courage or bravery to protect their employees in case of mistake is
detected.
16. There are
bad bosses who belong in a special class all their own.
17. There are bad
boss – who are a NARCISSISTIC, selfish, egotistical, egocentric, egoistical, If
you achieved well he would get angry with you because this in
his view you hurt his ego.
18. The bad bosses are people who he treated well, were those who would sit in meeting and not just say yes - but tell him what brilliant things he has done or work carried out in his career.
19. If you are
working in Private sector, then people can question their leaders. In the
private sector, barking orders and yelling like a drill sergeant isn’t going to
fly. In the private sector, you can’t turn everything into a 3 letter
abbreviation. He was an obsessive micro-manager, an authoritarian, and
super-paranoid. As a matter of fact, he used to brag about how he was a prepper
and had a big collection of weapons. Seemed like a psychologically unstable
person. If you are working in Public sector then, your bosses are having
tools of writing an adverse remark in confidential report about the employees
or subordinates.
20. If you
are working in Public sector then, your bosses are always threaten their
subordinate that a charge sheet could be issued for the mistakes in the work,
amounting to minor or major penalty.
21.Bad bosses in the
public sector treats the divisions or area allotted to be their kingdom and
employees as his slave to be ready for the orders. Bad bosses
utilise the staff for his private work at his house.
22. If you are
bosses in the section and your dealing assistants are male as well as female,
then you will get bad subordinates from Female or male. Bad Male
subordinates will come with employees Union to raise the issue for settlement
and Bad Female subordinates will came with personal problems, being a female to
reduce or hand over less work-load. Bad Female subordinates are also
habitual to come with her husband for stress in the work or tension. Bad Male
subordinates habitually very poor in performances or expert in making arguments
or mislead others, to slow down speed of on-going work.
23.Bad bosses are
always egoist or they pretend to be an expert and talented in everything though
they never actually taught anyone anything useful.
24.Bad bosses
are always likes dictatorship, tyranny, fascism, autocracy, where they prefer to
dictate their employees, who have to simply follow.
25. Bad bosses
will never appreciate the good work of their employees or avoid expressing
gratitude.
26. Bad bosses has no vision to lead their
employees or confuse them to shift the blame.
They lack a clear-cut, future-oriented plan, unstable about future
course of action.
27.Lack of positive
mind-set: Negative thinking can have several causes of adverse effects,
including personal traumatic experience. A bad boss often display a negative mind-set
characterized by excessive criticism, a
lack of trust in employees, always question about expertism of an employee
The boss often gets angry
and sometimes makes personal comments, which makes us very upset. Due to this
many times their work and personal life also gets affected. It is often seen that we do not like angry or
rude bosses. It is also seen that due to bad behavior, many employees make fun
of their bosses behind their backs or rally against them and try to teach them
a lesson. It is also very surprising
that the boss sometimes behaves indifferently, speaks ill of the working
professionals, and is seen talking very nicely after some time or the next
day. Seeing such behaviour, sometimes
you might feel that your boss is a victim of multiple personality disorder and
sometimes you might feel that the boss might have been in a bad mood for some
time. But have you ever tried to know its real reason? A group of executives tried to find out the reason for such rude
behavior of bosses and it came up with interesting results. In this, scientists
also focused on previous studies in which the impact of rude behavior of bosses
on employees was specifically studied.
======
While not all bad bosses exhibit dictatorial behavior, many problematic leadership styles can indeed resemble aspects of a dictatorship. Here’s why:
Characteristics of a Dictatorial Boss
- Lack
of Micromanagement: Dictatorial bosses often
control every aspect of a task, leaving little room for autonomy or
liberty or creativity.
- Lack
of Unity: They rarely seek or value
feedback, believing their way is the only right way.
- Fearful
workplace: These bosses may use fear
or coercion to maintain control, making the workplace stressful and
unproductive.
- Resistance
to Change: They often resist new
ideas, clinging to outdated practices because they fear losing control.
- No Sympathy: Dictatorial bosses may disregard employees'
well-being, focusing solely on results without considering the human
element.
- No Vision : Simply telling
the story of successful plan, can not lay down the vision for the
subordinate.
- No decision making: Bad
bosses always fear of wrong decision they may make. So, they delay in making decisions and
avoid embarrassment.
- Lack of Leadership : Bad
bosses always prefer to make over their responsibility on someone and
avoid good quality of leadership.
Impact on Employees and Workplace
a)
Low Morale: Employees feel undervalued and
unmotivated.
b)
High Turnover: A lack of trust and respect leads to
frequent resignations.
c)
Stifled Innovation: Fear of reprisal
discourages employees from sharing creative ideas or constructive criticism.
==
Penalty policies in professional software
development practice:
The penalties for poor performance by a software engineer in an MNC (Multinational Corporation) can vary depending on the company's policies, the employment contract, and local labor laws. Software Engineer team was headed by the team lead, and project head. They use to play a politicis and blame game in stead of concentration on resolving the issue or better service the clients, while the bosses headed by us ,was more interested in pacifying them, as they were fired by the top management, for work load is imposed upon them. As a client, we were expected to be smooth in functioning the project and pass on the benifits to the area team using the interface in the SSAs. SSA staff had no confident in the ITPC Staff of BSNL to the the project of the Data center. Morever, burden were passed on the Data Centers, without alloting the staff, as a result the works executed at the Data Center, were day by day deteriorated. It was being an harrashment on one side from the top management, other side by the sofware and SSA units.
There had been no proper transporation arrangement from Pune city to the Data Center. Even if a car of six seaters were arranged, but always made crowded or many hardship in travelling. The vehicles like car, bike, bus, cycle, Scooter, etc., move on the road on the mumbai national highway and addtionally, the area has been known to the industrial area of the pune city. So, we had to be pass many such multiple hardles and office management was also not keenly interested for such walfare activities of executives transportation. One has to apply with request to allot a seat in the vehicle coming in the route. The route was also so crowded by the office executives that it has to arrange a cronological list quarterly. The office was also grouped by many officers / employee's unions and association that affiliated to the political body. They use to create an influencing pressure from poltical leaders, on the office management for the facility or benifits. Public transprt including Corporation buses, Local train from Railway were very poorly managed. The Pune Mahanagar Parivahan Mahamandal Limited (PMPML) buses, while numerous, are often full, especially during peak times, due to the high number of commuters. Pune's local train system, which primarily operates on the Pune-Lonavala line, experiences high passenger volume, leading to crowded trains, all the time. Break-down of PMPL buses were a common phenomena and Local trains were also haulted on one or other railway station, so that express train could pass, without intrruption. Consequenly, trains and buses have given a very bad experiences on some or other day.
If you leave office Car, for personal reason, you have to travel changing three buses or train with two buses or authoriksha, being it was 50 km from Pune city. Even there had been no Canten facility or Liabrary or training in the software. There had been two types of executives posted at Data Center one- Engineering staff or technical staff and second - Accounts and Finance. Since Engineering executives were more in numbers than Accounts and Finance executives, Engineering executives, used to underestimate or insult in one or other way, to downgrade Accounts and Finance executives, for being it is headed by a technical bosses all the units of data center.
Typically, penalties are not punitive but aimed at addressing the issue and encouraging improvement. Here's an outline of possible following measures:
1. Formal Feedback and Performance
Reviews
- Description: The employee
may receive constructive feedback through a formal performance review.
- Purpose: Helps identify
areas for improvement and provides clear expectations.
- Example: Setting measurable
goals and providing support like mentoring or training.
2. Performance Improvement Plan (PIP)
- Description: The employee is
placed on a structured plan with specific performance targets and
deadlines.
- Purpose: Gives the
individual a fair chance to improve and meet the company's standards.
- Outcome: If the targets are
not met, further actions like demotion or termination may follow.
3. Reduction in Bonuses or Incentives
- Description: Poor
performance may result in reduced or no bonuses, commissions, or stock
options.
- Purpose: Links rewards to
productivity and effectiveness.
- Example: An underperforming software
engineer may lose their year-end performance bonus.
4. Reassignment of Roles
- Description: The employee
might be reassigned to a different team or project more suited to their
skills.
- Purpose: Aligns the
employee’s capabilities with job requirements.
- Example: Moving from a
high-pressure development role to a support or maintenance position.
5. Disciplinary Action
- Description: Repeated or
severe underperformance might lead to warnings (verbal or written).
- Purpose: Serves as a formal
record and precursor to further steps if performance doesn’t improve.
6. Termination of Employment
- Description: As a last
resort, the employee may be dismissed for failing to meet performance
expectations.
- Purpose: Ensures the team
maintains a high standard of work quality and efficiency.
- Example: This is usually
accompanied by severance pay or according to contractual terms.
Legal Considerations
- Local Laws: Companies must
comply with labor laws that protect employees from unfair dismissal.
- Notice Period: Termination
typically requires a notice period unless it’s a case of gross negligence.
- Employee Support: MNCs often
provide exit counseling or assistance to help the employee transition to a
new role.
Prevention Strategies
- Regular Training: Equip
engineers with up-to-date skills to meet job requirements.
- Mentoring Programs: Offer
guidance to employees struggling with performance.
- Feedback Culture: Regular
check-ins and feedback can prevent performance issues from escalating.
Key Takeaway
While penalties exist, most MNCs focus on creating opportunities for
improvement before taking strict action. The ultimate goal is to balance
accountability with support to help employees succeed in their roles.
If project is allotted to the MNC, for development of software and agreement thereof, specify the penalty clause, then MNC accepts penalty for poor or delay in performance.
===
A good boss serves as a
compass, steering employees toward success while fostering a culture of trust,
respect, and growth. This guidance benefits both employees and the company by
creating a motivated, capable, and cohesive workforce.
Good bosses are often referred to by
various positive terms that reflect their leadership qualities and the impact
they have on their teams. Here are some of the most common ways good bosses are
described as follows:
- 1. A good Leaders
- Why: They inspire, guide, and motivate their team to achieve goals while setting a positive example.
- Traits: Visionary, empowering, and decisive.
- 2. A good Mentors
- Why: They nurture talent, provide guidance, and invest in the professional growth of their employees.
- Traits: Supportive, patient, and knowledgeable.
- 3. A good Coaches
- Why: They help employees identify their strengths, overcome challenges, and unlock their potential.
- Traits: Encouraging, strategic, and goal-oriented.
- 4. A good Role Models
- Why: They demonstrate integrity, work ethic, and professionalism, setting an example for others to follow.
- Traits: Honest, ethical, and inspiring.
- 5. A good Visionaries
- Why: They provide a clear direction, set long-term goals, and create a sense of purpose within the organization.
- Traits: Strategic, innovative, and forward-thinking.
- 6. A good Servant Leaders
- Why: They prioritize the needs of their team and work to remove obstacles that hinder success.
- Traits: Empathetic, selfless, and people-focused.
- 7. A good Team Builders
- Why: They foster collaboration, trust, and unity among team members.
- Traits: Inclusive, communicative, and relationship-focused.
- 8. A good Problem-Solvers
- Why: They address challenges effectively while guiding their teams through difficult situations.
- Traits: Analytical, composed, and resourceful.
- 9. A good Motivators
- Why: They encourage their teams to stay focused, energized, and committed to their goals.
- Traits: Positive, enthusiastic, and charismatic.
- 10. A good trainer:
- Why: They provide emotional and professional support, creating a safe and productive work environment.
- Traits: Approachable, empathetic, and reliable.
- A good bosses are :
1. Passionate with his employees
2. Consistent in integration.
3. Cool-headed with their employees
4. Personable to be for the employee
5. Open-minded and friendly with his employees
6. Attentive
7. Humble
8. Decisive
9. Honest
10. Motivating
11. Appreciative
12. Sacrificing
13. Encouraging
14. Respectful.
15. Polite with their employees
16. Supportive.
17. Vision broad
18. Creativity
19. Positive mind.
20. Empathy
1. I worked
as Accounts officer for 29
years. He had many qualities that made him a boss I looked upto. He was a great
teacher, technically proficient, organized, hard-working and set ‘impossible’
targets for us and pushed us all to achieve them. My boss told me after
the meeting that your transfer from the city, is avoided, by showing your
performance upto the mark. He took the words from me that I have to
achieve upto the mark, to save my face.
2. My best bosses both treated me with respect
and kindness. They also would vary their style based on who they were working
with, which is a kind of respect. For example, they figured out what motivates
me (thanks and praise), and used it on me. They figured out what motivated
other people, such as a challenge, and used that on them. They were honest with
me about both my talents and my shortcomings, but did it tactfully. When they
criticized me, I felt they were helping me, not trying to put me down. I’ve had
bosses who had their own agenda, such as making sure they have the most power,
the most knowledge.
3. They ask the
employees for ways to fix problems, rather than sitting in an office dreaming
up things they think will fix problems, and imposing them on people.
4. My best boss
is someone who understands human beings, are human. We make mistakes. If you
can’t give as much leeway as you expect for your own mistakes, then you have no
business being in management.
5. A good boss
has an important role to play in creating a healthy work environment for
employees. It’s his duty to ensure that employees aren’t facing any problems
and good care is being taken of them at the workplace.
6. My
boss gave me the work of my interest and encouraged for excellent work.
7. My boss, who
has always respected me and recommended me for the training of my desire to
improve my know-how.
8. My boss,
forgot the mistake made by me and guided in peaceful low voice for the work
performances.
===
Best bosses in my
office life
1. Shiro : The boss
who understood the spark in me when I was at night duty at footpath.
2. Naik: The
boss daily took my exam test during lunch time in the office.
3. Swant, Shaky, Katt, Nileka, Desh CAO, :
Accounts level officers or executives, help me directly or indirectly
to guide or train me on job training or practically helped.
4. KCGK & Pund :
5. Bhole / Mohanrao at Jalna:
The year 1990 onward was a
blessing from my almighty Allah. My parents insisted me to get married,
as my all brother and sisters are happily married and well settled in their
family life. In my family, I was eldest boy who told my parents that I
would be ready for marriage only after an year or two.
My parents were forcing me to get
married according to their choice and threatening to choose the girl from your
choice or they will select her as per their choice, irrespective of educated or
uneducated or unemployed.
In fact, he had no girl friend or
choice in college life or after employment. Of course, there could have
been so many girls, who could have been my life partner or could have ready for
marriage.
This can often be due to the fact that when a guy hangs out with his
girlfriends (especially one-on-one), other (interested) girls often
automatically assume that the guy is already taken/on a date (with the girl
he's with). Girls/women usually often assume that when a guy is in a
group of friends and isn't interactive with a particular female then he's most
likely available. Whereas, if he's interactive with a female one-on-one it
might be a casual date. Even if a guy is with a group of girls, it's not
easy to tell if he's single and most girls/women see this as a most girls who
want to get serious with a guy don't prefer a guy who has a lot of girlfriends,
and once a guy hangs out with girls, he automatically attracts more (girl)
friends because that's the type of energy he sets.
It is happened a day when a father of two girls were sitting with my Uncle in a marriage told that father to choose my uncle’s son, wearing a fancy dress and hear-cut or choose me, so that we could proceed. I was wearing a poor dress and without a good looking, old-fashioned, as financial condition of my family was little bit bad and I was working for TV/VCR repair on part-time basis to meet my education expenses. I was sitting behind my Uncle, hearing their talks. I am shocked to listen the answer of that Father that he likes a good looking body and this old fashioned boy is not food looking. My uncle was knowing that his son has multiple girlfriends and romantic stories, while I had a girls but not girlfriends, as I like to make friendship with boy or with same gender. I understood that day that a father of girls searches their son in law, with good properties in his or his family's name.
It sounds like you don't have any expectations of dating with any of your current girls friends and your ability to get along so well with people of the opposite gender is something that many guys don't understand. Your friends could be super helpful in your quest to find a romantic partner. They would give you great feedback on a dating app profile! These are perfect people to help you take new pictures that best represent you and attract the type of woman you like. You could try to talk to them explicitly about how you are really interested in finding a romantic partner and you enjoy hanging out with them so much, be forward in expressing how you would appreciate any recommendations they have. Also, asking them to bring you with them when they attend any type of social event where there will be women you don't already know. Setting people up on a blind date might be difficult for someone for whatever reason, but it is way easier to bring you around and then let you do the flirting. For a woman, having another trusted woman vouch for a man being cool/safe, reduces a big initial barrier. I understood one thing that today, having a girl friends are treated as a big achievement.
It’s a generalization to say
that all girlfriends prioritize
wealth and properties over good character in their boyfriends.
While material stability can be important in relationships, many people value
emotional connection, trust, respect, and shared values over financial assets.
Here’s a balanced perspective:
Why Some People Value Wealth in
Relationships
1. Security and Stability
- Financial resources
often equate to stability, which is crucial for long-term planning, family
building, and a sense of safety.
2. Societal Pressures
- In some cultures,
societal norms and expectations place a high emphasis on financial success as a
measure of worth.
3. Lifestyle Compatibility
- Shared financial goals
and the ability to afford certain lifestyles can influence partner
selection.
******
CR Change request.
A Change Request (CR) is a formal proposal to modify a
product, service, system, or project. It is commonly used in project
management, software development, and IT processes to document and address
adjustments required to meet evolving needs or fix existing issues. There had
been no argument on our office side as client to protest against the demand of
CR. But it is habitual for the software engineer, to avoid up-coming
workload and ask for CR. It may be earmarked here that if original
software code is accepted by the Client or new addition in the existing
project, the demand of CR is justifiable, but if you ask for completion report
of original CR and acceptance is signed, then Software Engineer should not ask
for Cr.
What is a Change Request?
A Change Request is typically initiated when:
1. New Requirements
Emerge: Stakeholders identify additional functionality or features.
2. Issues Are Found:
Bugs or defects in a product/system need fixing.
3. Market or Business
Needs Change: Shifts in strategy require changes to scope, budget, or timeline.
4. Regulatory Compliance:
Adjustments are necessary to adhere to legal or industry standards.
Components of a Change Request
A CR typically includes:
1. Description: Clear and
detailed explanation of the requested change.
2. Reason for Change:
Why the change is needed and its expected benefits.
3. Impact Analysis:
Assessment of how the change will affect scope, timeline, budget, and quality.
4. Priority Level:
Urgency and importance of the change (e.g., high, medium, low).
5. Approval Status:
Records of who has reviewed and approved the change.
6. Implementation Plan:
Steps required to execute the change if approved.
CR Workflow Process
1. Initiation
o Change request is
submitted, often through a tool or form.
2. Evaluation
o Assess its
feasibility, risks, and impacts (technical, financial, and timeline).
3. Approval/Rejection
o Decision made by
stakeholders or a Change Control Board (CCB).
4. Implementation
o Approved requests are
incorporated into the project or product roadmap.
5. Verification and
Closure
o Changes are tested,
validated, and formally closed.
Tools for Managing Change Requests
Popular tools include:
- Jira
- ServiceNow
- Asana
- Trello
- Microsoft Project
Key Takeaway
Effective management of CRs ensures that changes align with project
goals, minimizes risks, and maintains stakeholder satisfaction while avoiding
scope creep.
A Change Request Form serves as a formal document to propose, evaluate,
and implement changes to a project, system, or product. It ensures that all
relevant information is documented and communicated effectively. Here's what
should be included in a comprehensive change request form:
1. Basic Information
- Request ID: Unique
identifier for tracking the request.
- Date of Request: When the
change was submitted.
- Requester Details: Name,
role, and contact information of the person submitting the request.
2. Change Description
- Title/Subject: A concise
summary of the change (e.g., "Update to User Interface Design").
- Detailed Description: A
clear and thorough explanation of the requested change.
3. Reason for the Change
- Justification: Why is this
change necessary? Include background context and any issues it addresses
(e.g., fixing a defect, meeting regulatory requirements).
- Expected Benefits: Outline
the advantages, such as improved efficiency, cost savings, or user
satisfaction.
4. Impact Analysis
- Scope Impact: How the change
affects the project’s objectives or deliverables.
- Time Impact: Additional time
required to implement the change.
- Budget Impact: Cost
implications, including additional resources or tools needed.
- Risk Assessment: Potential
risks and mitigation strategies.
- Dependencies: Other systems,
tasks, or teams that might be affected.
5. Priority and Urgency
- Priority Level: Indicate
whether the change is critical, high, medium, or low priority.
- Implementation Timeline:
Proposed or required deadline for the change.
6. Approval Workflow
- Stakeholder Review: List of stakeholders who
need to review and approve the change (e.g., project manager, client, team
lead).
- Approval Status: Space to record the decision
(e.g., approved, rejected, or deferred) and any comments.
7. Implementation Plan
- Action Steps: Detailed tasks
required to execute the change.
- Responsible Parties: Names
and roles of individuals or teams accountable for implementation.
- Testing and Validation:
Steps to ensure the change is correctly implemented and meets
requirements.
8. Supporting Documentation
- Attach any relevant files,
diagrams, or data to support the change request. Examples include:
- Requirements documents
- Test results
- Design mockups
9. Follow-Up and Closure
- Post-Implementation Review:
Space to record the outcome of the change and verify success.
- Closure Sign-Off: Final
approval from key stakeholders to close the request.
Key Features in a Change Request Form
- Clear structure and concise
sections for easy comprehension.
- Flexibility to accommodate
different types of changes.
- Integrated digital tools (if
possible) for efficient tracking and management.
A well-designed form ensures that all aspects of the change are
considered, leading to better decision-making and successful implementation.
====
Validation and testing of software before
deployment are crucial steps in ensuring that the system functions as intended,
meets requirements, and is free of significant defects. These processes reduce
the risk of introducing errors into the live environment and ensure a smooth
user experience. Here’s an overview:
1. Importance of Validation and Testing
- Prevent Errors: Identify and
fix issues before they reach end-users.
- Ensure Quality: Confirm that
the software meets specifications and quality standards.
- Minimize Downtime: Reduce
risks of crashes or failures in the production environment.
- Enhance User Satisfaction:
Deliver reliable, functional software to users.
2. Validation vs. Testing
- Validation: Ensures the
software fulfills the intended business requirements (i.e., "Are we
building the right thing?").
- Testing: Focuses on
verifying that the software functions as designed (i.e., "Are we
building it correctly?").
3. Types of Testing Before Deployment
Functional Testing
- What It Tests: Ensures the
software meets specified requirements.
- Examples:
a)
Unit Testing: Testing individual components.
b)
Integration Testing: Verifying interactions between
modules.
c)
System Testing: Ensuring the entire system works as
expected.
Non-Functional Testing
- What It Tests: Evaluates
system performance, security, and usability.
- Examples:
a)
Performance Testing: Assessing speed, scalability,
and stability.
b)
Security Testing: Identifying vulnerabilities or
weaknesses.
c)
Usability Testing: Ensuring the system is
user-friendly.
Regression Testing
- What It Tests: Ensures that
new changes do not adversely affect existing functionality.
II.
Acceptance Testing
- What It Tests: Validates the
software against business requirements and user needs.
- Examples:
a)
User Acceptance Testing (UAT): Performed by
end-users to verify it meets their expectations.
b)
Alpha/Beta Testing: Early-stage testing with
internal teams or selected users.
4. Validation Processes
a) Requirements
Validation
b) Confirm that the
documented requirements align with stakeholder needs.
c) Design Validation
d) Verify that the
software design can achieve the desired functionality and performance.
e) Prototyping and
Simulations
f) Use prototypes or
mockups to validate the system's behavior early in development.
5. Pre-Deployment Checklist
a)
Code Review: Peer-review of the codebase to
identify potential issues.
b)
Automated Testing: Utilize tools to run tests for
scalability, security, and performance.
c)
Configuration Management: Validate environment
settings and dependencies.
d)
Backup and Rollback Plan: Ensure a plan is in place
to revert changes if needed.
6. Tools for Validation and Testing
a)
Functional Testing: Selenium, JUnit, TestNG.
b)
Performance Testing: JMeter, LoadRunner.
c)
Security Testing: OWASP ZAP, Burp Suite.
d)
CI/CD Pipelines: Jenkins, GitLab CI/CD for
automated testing and deployment.
7. Testing Environment Setup
a)
Development Environment: Used for initial coding
and unit testing.
b)
Staging Environment: Mirrors production and is used
for final validation and testing.
c)
Sandbox Environment: Isolated environment for
testing without affecting live systems.
8. Key Best Practices
a) Begin testing early in the development cycle.
b)
Implement automated tests for efficiency and
consistency.
c) Involve end-users in validation processes to ensure
real-world applicability.
d)
Document and track all test results for accountability
and analysis.
===
Implementation
of GST in the code, was quite expensive in india
The implementation of GST (Goods and Services Tax) in
India brought about a significant overhaul in the country's taxation system. It
unified multiple indirect taxes into a single tax system, simplifying tax
structures but also leading to challenges and costs, especially in the digital
and software sectors.
Why Implementation of GST in Code Was
Expensive
1. Complex Tax Structure
a)
GST rates vary depending on goods and services, with slabs like 0%, 5%,
12%, 18%, and 28%.
b)
Businesses had to update their software systems to accommodate these
multiple tax slabs and ensure compliance.
2. Massive Code Overhaul
a) Existing systems needed a complete redesign to integrate GST logic.
b) Features like reverse charge mechanism, Input Tax Credit (ITC), and
state-wise bifurcation of GST (CGST, SGST, and IGST) added complexity.
3. Compliance with Evolving Rules
a) GST rules and compliance requirements frequently changed after its
rollout.
b) Software needed regular updates for e-invoicing, GST returns (GSTR-1,
GSTR-3B, etc.), and reconciliation.
4. Increased Development Time
a)
Implementing GST required in-depth analysis of the tax structure, coding
logic, and integration with financial and billing systems.
b)
This extended project timelines, increasing costs.
5. Testing and Validation
a)
Rigorous testing was required to ensure the software correctly
calculated taxes, generated GST-compliant invoices, and integrated with
government GSTN (Goods and Services Tax Network).
b)
Mistakes in taxation could lead to penalties, increasing the need for
accuracy.
6. Integration with GSTN
a)
Businesses needed to ensure their systems could connect with GSTN for
return filing and data reconciliation.
b)
GST Suvidha Providers (GSPs) added another layer of cost for API access
and services.
7. Training and Expertise
a)
Developers and financial teams needed training on GST compliance, adding
to implementation expenses.
b)
Hiring experts to design and oversee the process further escalated
costs.
Challenges Faced
1. SMEs
Struggled with Costs
Small and medium enterprises faced a significant financial burden as they had
to transition to GST-compliant ERP or billing software.
2. Frequent
Updates
The constant updates in GST rates, exemptions, and rules meant software
providers had to regularly revise their solutions.
3. Infrastructure
Requirements
Ensuring seamless connectivity with GSTN required robust infrastructure, which
many companies lacked initially.
LEASE CIRCUITS
KT FOR
MODULE-WISE
billing of Pune SSA and attended its related issues.
Validation testing of new codes
PMS related issues and its other related activities.
Major Billing issues and its co-ordination with SI
Resolution of PMS L1/L2/L3 dockets..
Finalization of SLA clauses in AMC & O&M etc,
Verification of Invoices raised by SI for AMC & O&M
etc,
Migration activities of FTTH, DSPT, IN-SERVICES etc.,
===
LL SSA sign off process was politically motivated:
On posting of Four JAOs were joined to the Accounts team, headed by me, GM F asked the head or his next subordinate to take up for Landline SSA sign off. He has also explained all of them, the strategies for SSA sign off with the data to be obtained from migration team. He has also handed over proforma of SSA sign off so that head of the SSA could sign off with the certification with SSA IFA.
No comments:
Post a Comment