Download link : Risk Assessment Checklist Risk Assessment Checklist Project Name Project Code Program Manager Project Manager 1 Engineering Process 1.1 Requirements Item Yes No NA Remarks Stability Are the requirements stable  Are the external interfaces changing Completeness Are there requirements you know should be inthe specification but aren’t? (IF […]
Download Link : scrum-tmpl-100212
Download Link : Proposal Template <Company Logo> Proposal To <Client Logo> <Client Name> For <Services Offered / Project name> <Date: dd-mm-yyyy> <Company Name> <Company Address> <Phone> <Fax> <Website> Table of Contents 1. Response to RFP.. 3 2. Executive Summary.. 3 3. Company […]
Download Link : Proposals and Contracts Procedure_1 Proposals and Contracts Procedure Version1.0 S.No Description Version No Requested By Authorized By 1. Initial 1.0 NA 1. Objectives The objective of this procedure is to define and establish the process of generating and submitting […]
Download link : sample issue tracker spreadsheet
Always Have a Single, Authoritative Source For Your Schema Everyone should know where the official schema resides, and have a frictionless experience in getting a fresh database setup. One should be able to walk up to a computer, get the latest from source control, build, and run a simple tool to setup the database (in […]
Like many conveniences in software development, a shared database is a tar pit waiting to fossilize a project. Developers overwrite each other’s changes. The changes I make on the server break the code on your development machine. Remote development is slow and difficult. Avoid using a shared database at all costs, as they ultimately waste […]
We talk endlessly about improved software quality and reduced risks, but deployable software is the most tangible asset to “outsiders” such as clients or users. The importance of this point cannot be overstated.
You can manage scopes of time, cost, and quality much more effectively by basing your decisions on working software with actual feedback and metrics, not just task items on a project schedule.
A set of requirements is complete if and only if it describes all significant requirements of concern to the user, including requirements associated with functionality, performance, design constraints, attributes, or external interfaces.