| |
| |
See Also
Best Practices for Software Projects - Risk Management.
More...
Beyond Broken Links. More...
Minimizing Software Defects via Inspections.
More...
Testing GUI. More...
Test Methods. More...
Test Reviews. More...
Weekly Status Report
Sample. More...
Stocking and Managing a Test Lab.
More...
Best Practices for Software Projects
- Software Measurements. More...
Improving the Quality process by
doing the
Metrics Calculation
Download
Documentation Tips. More...
|
|
|
| |
Learn more material at a Fraction of Price!
Get the training that will help you
face the challenges and meet the demands of today's competitive market place.
Programs
Offered: Oracle DBA, Cisco Networking,
Software Testing & Programming. More...
|
|
|
| |
Find out which Bug-Track.com account is right
for your software development team, Try our Demo Now!
|
|
|
| |
Promote Your
Products and Services
SQAtester.com Storefront Program is the best way to help companies Promote their Products and
Services. More...
|
|
|
| |
WAPT
is a load and stress testing tool for web sites and intranet applications with web interface. Accurate load simulation,
run-time test data generation, recording and playback of secure HTTPS requests, clear graphs and reports, and More...
|
|
|
|
|
 |
|
|
|
|
|
Your information should be available at your
fingertips.
We can make this possible. More...
|
|
Very few projects go as planned. Many projects encounter
problems that must be corrected and a few lucky projects go smoother than planned. Regardless of how successful
or disastrous a project is, it is important to review the project in detail once the project is over. This allows
your team to figure out what things were done well and to document the things that need improvement. It also aids
in building a knowledge base that teams coming behind you can review to ensure they get the most out of their upcoming
projects.
|
| Tips for Conducting Project Post Mortems |
 |
___________________ |
|
The key to a successful projects is to learn from past
mistakes. Below is a list of 5 Tips
for conducting successful Post Mortem reviews:
1. Plan Your Post Mortem Review - Upon completion of a project, the Project Manager should
conduct a "Post Mortem" review. This is where the Project Manager invites all the major players of the
team (Analysts, Lead Programmers, Quality Assurance Leaders, Production Support Leaders, etc) to a meeting to review
the successes and failures of the project.
2. Require Team Participation - Ask the attendees to bring a list of 2 items that were
done well during the project and 2 things that could be improved upon.
3. Hold the Post Mortem Review Meeting - Go around the table and have each person to discuss the
4 items they brought to the meeting. Keep track of how many duplicate items you get from each team member. At the
end of the round table discussion of items, you should have a count of the most popular items that were done well
and the most agreed upon items that need improvement. Discuss the top 10 success items and the top 10 items that
need improvement.
4. List Items Done Well and Things
Needing Improvement -Upon listing
of the 10 success and improvement items, discuss specific things that can be done to avoid the items that need
improvement upon the next release. If some items need more investigation, assign specific individuals to finding
solutions.
5. Create a Post Mortem Report - The best way to keep this information organized is to
create a "Post Mortem" report, where you document your findings. Send the Post Mortem report to all team
members. Before team members embark on their next project, make sure they review the Post Mortem report from the
prior project to gain insight from the prior project.
 Share your thoughts on Tips for
Conducting Project Post Mortems
in SQAtester Group.
 E-mail to a Friend.
|
|
Manage all phases of your software
development with
Software Planner
Software Planner is a project collaboration tool
that allows you to manage all phases of your software development. In the initial stages of the project, it allows
you to post functional specifications and post project related documents (like meeting minutes, client proposals,
etc.). As the project progresses, it allows you to post baseline documents (like detailed designs and project plans).
As development proceeds, it allows your project managers and developers to track project deliverables.
The developers can update the percentage complete for all items assigned to them. Once testing begins, it allows
your testers to create test cases and track software defects. Developers are automatically alerted, by email, as
defects are assigned to them. Team members are alerted as new documents are uploaded or re-uploaded (like project
plan updates, etc.). And each person has the ability to control the email alerts they wish to receive. Use the
discussion forums to communicate all issues with clients and project team members. Keep your appointments and to
do list on-line and updated at all times.
Try Software Planner FREE for 2 weeks.
|
| Books to Read |
|
________________________________________ |
|
|
|
Quality Web Systems
This book provides a framework for ensuring that key Web system success criteria are addressed during the development
of a Web system. Detailed technical guidance is provided for all criteria, along with testing strategies that allow
for verification of a quality implementation. More...
|
|
|
|
Automated Software Testing
Written for those with some background in software engineering, Automated Software Testing: Introduction, Management,
and Performance delivers a rigorous guide to the state of the art in managing automated testing in a text that
will benefit anyone who tests software for a living. More...
|
| Categories |
|
________________________________ |
| Community |
|
________________________________ |
| Specials |
|
__________________________________ |
| Millions of titles discounted up to 40-90% off. Great
low prices on your favorite books. More... |
|
Find all of your favorite software.
More... |
|
|
