A short Notes on Release Management.

Dear Reader / Friends,

This is my resume to write blog, post COVID-19. Almost it was tough 2 years for us. So here I’m sharing a short note throughout my experience to playing a Middle Management role with hope, it may help other in their role.

Excited to see your comment and experience to improvise further.

Discalimer: English is not my first language. Sorry for Error

Divided into three (3) main bullets points.

  1. Effective Communcation.
  2. Mission of Job.
  3. Release Management.

#Effective Communication

1. Communicate better & Co-Ordinate better.

                          – Keep smile 🙂 always & spread energy.

– Be a good listener.

                          – Note the Actionable.

                          –  Clear ask & delegation of statement of work with deliverable GOAL and define ETA.

2. Use Data to talk.

                          – Produce artifacts.

                          – follow the GOAL ETA.

                          – Show the progress and roadblock.

                          – Raise your hand for support to WIN, to avoid delay.

3. Unlock a network effect.

                          – Cross Team Co-ordination.

                          – Follow the effective media to communicate. Like If you can meet then meet, If not then call, if not then email and last but not least reached to His/Him next level RM.

                          – Tips, Use meetings (Online or offline) avoid email trails that create delays and sometime communication gaps.  

4. Not everyone, told to everything in details.

                          – Know your audience.

                          – C class executive has only interested to see business benefits and CapEx/OpEx to deliver your project.

                          – Architects / Middle Level interested to see your low level plan.

                          – Be professional and transparent to deal with partner.

5. Use reputation & Consistency.

                          – Earn believe following deliverable commitment.

                          – Sharing knowledge and producing documentation.

#Mission of Job.

1. Growth.

                          – Grow your knowledge to know business.

– Grow your skills to solve the problem.

– Look for appreciation.

2. How it’s drive a value to business?

                          – Who are the material users in market?

                          – Connect with NOC & Program Manager to know application impact in market.

                          – Know the revenue loss.

3. Understand the application or product need to run.

                          – Invite or meet them to know their application & deployment design.

                          – Interview them to collect their feedback.

4. Know How to connect to the application owner?

                          – Invite Application owner for enablement.

5. Think about your valuable contribution!

                          – Feel proud during solving problem.

                          – Be Mentor to help others to solve things quickly.

#Effective Release Management

1. Define the problem Statement.  

                          – Know the business pain.

                          – Know its impact to user experience.

2. Define Your Audience.

                          – Who has impact?

                          – Know your users’ expectation.

3. How to Define your Audience.

                          – Identification of unique sample.

                          – Android User, iOS user and web-based users.

                          – Tech Geeks or Layman.

4. Consider audience pain points.

                          – Capture the feedback.

                          – Document the actionable items.

                          – Set the action Priorities.

                          – Monitor it till delivery.

5. About success & failure.

                          – Do the demo & prototype simulation.

                          – Disclose the limitations

                          – Share the pre & post improvement benchmarks.

                          – Connect to user or business for feedback.

                          – Assess the feedback for agreed deliverable GOAL.

6. Risk & Limits

                          – Use disclaimer, where ever required.

                          – Highlight the limitations.

                          – Don’t assume anything.

Thank you & Regards

– Kuver P Singh