Situation - What action will you take to achieve code quality ?
1. Keep language specific code review guidelines and Naming Conventions document handy for the developer to refer before he writes any single line of code.
2. Peer Review
3. Code Analysis Tools. Ex: VS2010 Code Analysis, StyleCop, FxCop, NDepend, SPDispose Checker.
4. Code should be unit tested using Tools like NUNIT, Visual Studio Testing Framework.
Situation - Developer unable to deliver as per the estimate/plan.
1. Insufficient training may be one of the issue. What type of training is required ? Domain Knowledge or Technical.
2. Attach a senior resource/domain analyst to guide the developer in his work.
Situation - Large number of UAT issues.
1. Revisit your system test cases. They may not cover the complete functional testing.
2. Engage a Domain Analyst to review the system cases.
Situation- Unplanned leave schedule of the Team is impacting delivery
1. The first activity that a PM should take up at the start of the project is to maintain a leave calendar for the team in a shared location. Team member should update their leave plan well in advance for better planning.
Situation - What is the best way to manage bugs in the System ?
1. Identify a tool to manage bugs or issues.
2. Classify the bugs as per their severity i.e High, Medium and Low.
3. Assignment of bugs to resources as per their severity/complexity.
4. Initial Estimation of bugs/issues by resources.
5. Actual Estimation of bugs/issues by resources.
6. Set the status of the bug i.e. Unable to Reproduce, Code Complete, Closed, Open, Waiting etc. with proper comments.
Situation - Re-open Bugs
1. Root cause analysis.
2. Insufficient Test cases.
Situation - Client has the option to change the requirement anytime during the development.
1. Ensure you have configured your Repository (SharePoint etc.) to send alert whenever there is a change in requirement.
2. Analyze and do an impact analysis as the next step. Artifacts can be impacted - Source Code, Unit Test Cases, System Test Cases, Build Script etc.
3. Impact on estimation
4. Communicate the Client about the impact
5. Implementation of the change of requirement.
Situation - Code coverage/review/refactoring is missing during project execution
1. This is a common problem in software projects. The team miss some important activities like code review/unit testing/refactoring etc. under delivery pressure. There is a need for monitoring the process during the execution and enforce the process to ensure quality delivery. Escalate the issue.
Risk management breakdown in software projects -
Friday, August 5, 2011
Project Management Tips
Labels:
Project Management Tips
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment