Project Management Lessons Learnt

Configuration Mgmt Release Management PMD Rules, Sonar/Hudson Security Scan and Fixes Technology RoadMap Licensing Models Performance Benchmarking PA-DSS SPMM Process Governannce and Adherence Smart Scrum/STM Coes and Regular Interactions Integration ARB CAB Deployment and Rollout Risk Register Learning and Compentency Register Resource Fluidity and Managment Tracker. (biweekly reviews)

Requirement Docs/Design Docs/DataModels take time to read, but it must be read. Ask the right questions to team..you cann't review everything..but you should check as much as you can...and cover the rest by random checks and asking questions..clarifying your doubts..getting handson with poduct usage...coding, testing and reviews.. At all times, a high level schedule and low level schedule should be available, Every day at Eod , or at start, it should be updated with latest. Scrums should be made more evidence oriented or check randomly artifacts/process compliance of few. Even if there are scrums, just like WSR is shared with customers, entrust leads to share their track progress daily data points . it should be very granular. Individuals should track their productivity /FP. Review Week's and log lesson's learnt.

Induction to be formal with functional and technical walkthroughs. Logs needs to be maintained. Videos on product features can be used. SME / Backup SME / Volunteer list should be published. Major Decisions should be formally communicated (besides meetings, email for records). Meeting with RMG should be periodic. Inspite of daily standups, atleast once a  fornight meet with formal agenda. Review Daily Progress to minute detail of each assoicate via a tracker/tool smart scrum etc. Every other days review meetings with deep dive on tech or process are a must. Leave Tracker. Competency Development Tracking in icalms. Part of Goal Sheet. Mandatory 1 hr Learning Session every week. Thank you Thrusday...recognize and appreciate good work/initiatives. Risk Review Meeting every week with leads, once in two weeks by Management. Right Size Team. Read Each E-Mail and Doc. Clear Backlog of Docs Daily. Share review daily. Have right backups and BCP of physical and electronic re...

Lessons Learnt: If your team don't have full time designers and the design tasks have been entrusted to folks with coding experience but relatively no design experience, besides internal review few things needs to be done... Get some design templates from other teams/groups Own it and sit with Team,Designers,Architects and create a Table of Contents Assign small sections to be completed in  a day and review at eod Then setup Review with Architect and others who have designed for review atleast twice in the first week. Track daily each section  prohgress and press hard for things to be thought... Engage your best resources to review and when draft is ready start external review by other designers in group or outside. Internal Plan should be granual to a day's level. External plan should have IQA/EQA reviews for each deliverable. Not doing this..saw internal review highlights needs of a template first..lost a  week Next review highlighted gaps..in analysis...

How to effectively Track Design Progress in a Release? I estimated we should take 3 weeks and just put a single WBS element Design Doc. High level plan has design task with 3 weeks.. But when the design time started, one week down the line, I will feeling jiterry on how to track the design progress better? may be one approach   -Internal Review workshoop-1 on Week-1 end   -Incoprorate Comments   -Internal Review-2 on Week-2.   -External Design Review Workshop? I can also think of progress as    identify packages, flow , changes to each layer of the product for the functionality added/updated.