Final Progress Report Format: Fill & Download for Free

I was in my 9th grade year and I had to get my progress card signed by my parents. Unfortunately, my mom wasn’t in town, so I had no other option than to go to my Dad’s work and get my report card signed.That was the first time I saw him like that. My dad worked as a mechanical fitter in Railways. On that day, when I saw him, he was wearing a shirt which was torn near the sleeve. He was full of grease, wearing a plastic cover on his head to avoid the grease falling on him. I was not able to control my tears, but went silently and showed my progress report. It took almost five whole minutes for him to clean his hands. To his surprise I was failed in a subject. He looked at me and did not utter a single word. To my disbelief, he signed the progress report silently. Then, he asked if I was hungry. He took me to a tea shop nearby and got me some tea and biscuits. I returned full of tears in my eyes. I wish I had never seen him in such a way.But, that changed the course of my life. It would be lie if I said I never failed again. However, I ensured I won’t fail in my life. I graduated from school and college as an average student and struggled so much in my career. Finally, I found a respectable job and can say now my parents are truly happy.As children we are so busy finding the faults and pointing at our parent’s mistakes. We never realize or see the sacrifices they make. We never see them slip. Have you seen them eat the rotten side of the apple? Have you seen them praying for themselves? Most parents live for their children and die for their children.The sad part is, some people are ashamed to bring their parents in front of society. For those of such nature, I honestly believe karma will hit them back in the form of their children.That’s my happy family during my engagement!!!

Background:I'm a final year B.E computer science student in an Engineering college in Bangalore. We need to submit a project as part of our 8th sem syllabus.Event: Project approvalWe(team of four) did a little something as a proof of concept for our project. Our judge panel there were 3 professors and Our HOD ( Head of department) and they gave it a go for our project. Our HOD was assigned as our project guide and our project coordinator told us that he(HOD) only volunteered to be our project guide.these incidents happened recently. here is a list of facepalm moments.The first week of our projectwe had to get our HOD's , guide's , Project coordinator's and Class teacher's signatures( yeah! that's a lot of work.. sigh) as part of our "progress check" routine.we went to our HOD's office to get his signatures. Following conversation took place between us in his office..HOD: enappa? en beku?(what you need?)Us: Sir, progress report alli signature bekithu(we need your signature on progress report?)he signs in the HOD column, and gets back to his workUs: sir, you didn't sign in guide column..HOD: naan a nim guide?(I'm your guide? )Us: haudu sir ( yes sir)HOD: naan yako nim guide aade?(Why did i become your guide?)Us: sir... ( speechless!)we didn't go for his signatures for few weeks because we were either too busy or too lazy (mostly lazy)After few weeks, we couldn't find our progress report so we got a new one and had to get all previous week's signatures.. In HOD's office again..HOD: enappa?(what you need?)Us: sir, progress report alli signature bekithu(we need your signature on progress report?)HOD: yen ella empty ide? elli previous week's signatures?(why is every column empty? where are previous week's signatures?)Us: sir, actually progress report misplace agide(sir, we have misplaced our progress report)he gave us an angry expression, thenHOD: first nim guide du signatures hakiskond banni(first get your guide's signature)Us:neeve sir nam guide(sir, you are our guide..)HOD: naan nim guide a?(I'm your guide?)Us: yes sir...then we were convinced he will remember us...We had Project Open house for project exhibition yesterday (May 6th)we got second prize for our project, ironically our HOD was called to give us the prize. After a little photo session, on our way back to our seats,HOD: guide yaru?(who's your guide?)Us:neeve sir.. (you, sir)We still need to get his signatures on our project report, and we still "hope" he will remember us!

I've never been a junior associate at McKinsey, but I have been a business analyst. From what I recall, junior associate is the title for the same role in India. The roles are basically the same, with a few regional differences including office culture and travel schedule (India travels Monday-Friday, whereas the US travels Monday-Thursday).I'll describe my experience for you, with the caveat that these things vary by office and project. I'll split my experience up into what it's like when you're on a project and when you're in between projects.When you're on a projectGetting staffed on a new project as a business analyst often feels like you're starting a new job. You're working with people you've never worked with before on subject matter you're likely not familiar with. Your first week on the project you're typically not very productive; a lot of your time will be spent reading documents to get familiar with the project and client context. Typically the weekend before you start, the project manager will send you a dump of documents to read over the weekend and during the week. These can include readouts from past projects with the client, the LOP (letter of proposal), and PDs (practice documents) related to the topic of your new project. In addition to reading documents, you'll typically be tasked with easy, rote tasks like making updates to a specific powerpoint page, running an analysis in excel, etc.One important distinction to make is whether a project requires travel or not. This impacts your life significantly. If a project requires travel, Tuesday and Thursday are travel days. You'll be getting up at the crack of dawn on Monday to head to the client site, and leaving mid-afternoon on Thursday to head home. Business travel seems glamorous at first, but most people tire of it quickly. Local studies are typically prized and seen as a luxury at McKinsey.For a non-travel day, a typical schedule could be:7:00 am: Wake up, check the flurry of emails that came in overnight, respond to anything urgent, shower and get dressed8:00 am: Grab breakfast in the hotel lobby and head to the client office8:30 am: Process check-in with the team's low-level client liaison to discuss progress since yesterday, plan for today, and any outstanding issues / questions9:00 am: Run an analysis on some client data that you've finally received after days of haggling back and forth11:00 am: Problem solving session with the partner / associate partner on the project (details on problem solving follow later)12:00 pm: Head to the nearest food source to pick up lunch; most projects bring lunch back to their desks and continue working1:00 pm: Work on slides for the next steering committee / progress report based on the outcome of problem solving4:00 pm: Progress report with 2-5 key clients; as a business analyst, you'll be taking notes and addressing any direct questions on the pages / analyses you worked on6:00 pm: Internal team meeting to debrief from the progress report and align on what needs to get done by the next day7:00 pm: Order dinner and continue working on the outcomes from the progress report10:00 pm: Head back to the hotel to wrap up any loose ends, work out, and sleepFridays are typically easier. The team disperses and works in their own offices. You'll typically have a few project conference calls on Friday, and some work to take care of, but most people spend a good chunk of their time on Fridays socializing with people in their offices. Fridays are also typically shorter days, running from 8:30-5:00 on average, with happy hour in the office in the evening.One last thing I'd like to note about time spent on McKinsey projects is that they typically feel like a series of deadlines. The sequence alternates between team problem solving and an important client meeting (either a progress report or steering committee). I'll briefly describe each of these here:Problem solving - Much has been made of the McKinsey problem solving method, but team problem solving is quite simple. Before problem solving, the team is usually scrambling to prepare the draft document for the next big client meeting. During problem solving, the project leader presents the draft document while team leadership (associate partners and above) gives feedback. It can get quite argumentative, and everyone is encouraged to jump in. The output of problem solving is usually alignment on what work needs to be done to finish preparation for the next client meeting.Progress reports / steering committees - These are when you meet with the client that pays the bills, and usually several other members of the project team. The agenda usually revolves around a project update (both on the process and the conclusions the team has made so far). These can be stressful, as the outcome of the meeting usually determines your quality of life for the next few days. Happy clients = happy life, so a good progress report is reason for celebration.Between projects / staffingThe staffing process is one of the biggest aspects of consulting that gets glossed over in information sessions and interviews. When you start at McKinsey you'll be assigned a PD (Professional Development) manager. They are in charge of helping you to find projects. They have one of the hardest jobs at the firm, as they are constantly getting pressure from partners to staff people and keep utilization up, while dealing with requests from consultants that want to wait for the perfect project.For your first project or two, you're basically assigned to a project without your input. It's like being deployed in the military. After that, once you've proven yourself to be a useful asset to a project, you'll have a lot of input in the projects you choose. The best way to get a new project at McKinsey is through your network, rather than waiting for PD, so typically in the last few weeks of a project you'll be reaching out to people you know to see what else is coming up. You'll also be having calls with PD to discuss your plans for after the project.A lot of the time you'll be going directly from one project to the next, but occasionally you'll find yourself with 'bench time', also known as 'beach time'. This is time between projects when you're not assigned to anything. Typically during this time consultants will help out with other things around the office, including proposals and knowledge work. 'Beach time' is another envious luxury at McKinsey.ConclusionsThis turned out way longer than I expected. I must re-emphasize that the above is generalities from my experience, and I've left out a lot of the complexity in working at McKinsey so I don't end up writing a novel here. In particular, problem solving can be a lot more complex than just preparing a document for a meeting.I hope this helped - cheers!