The 10 Do’s and Dont’s When Building a Software Project
My name is Cheyne Phillips and I am a Senior Project Manager at Endertechnology. I would like to share with you the 10 common mistakes I see that prevent a successful Software Project launch. Following the Do’s and avoiding the Don’ts will ensure a successful Software Project.
- Do Meet Everyone Involved In the Project
Don’t assume you have met the entire team. Stakeholders, Investors, Product Owners, Project Managers, Testers, Developers, Subject Matter Experts, and Architects comprise a team. Failure to meet all key players will cause communication issues down the road.
2. Do Understand The Project From The Business Side
Don’t write a proposal without first understanding how the business operates. Typically software projects have a targeted Return on Investment in mind. To hit this target, the development team needs to understand how the product will be the catalyst for the ROI.
3. Do Know The End User
Don’t make design or functionality choices without consulting a Subject Matter Expert. This established expert is the voice for the intended user of the product and their knowledge should be respected to shape the product.
4. Do Establish Bi-Weekly Meetings
Don’t extend or cancel these meetings. These meetings will serve as planning sessions, progress updates, demos of work completed, and idea gathering sessions. Setting the precedent up front that these meetings are mandatory provides a roadmap to success.
5. Do Establish Roles For The Entire Team
Don’t rely on the organic forming of a team. It is crucial that roles are set up front. Business Owners, Product Owners, Scrum Masters, Developers, Testers, Subject Matter Experts all have to stay in their respective lane. A Breakdown in this process will deviate from an Agile Scrum Methodology to a Waterfall Development Methodology.
6. Do Use Project Management Software
Don’t rely on spreadsheets and documents. Proven Software like Jira has features designed to keep teams organized and on track.
7. Do Create Extensive Backlogs
Don’t rely on ideas being remembered during meetings. Everything should be documented and arranged into the backlog with an agreed upon format. Stories, Bugs, Epics, Versions, Estimates, are good examples of comprehensive backlogs.
8. Do Estimate All User Stories And Tasks
Don’t rely on a single estimate. Having the entire team assign levels of effort to each task will provide the most accurate estimate. Accurate estimates will provide everyone with the clarity to establish dates of delivery.
9. Do Provide Testing Level Estimates
Don’t only have development estimates. Providing each story and task with a level of effort required to pass or fail is important. Failure to accommodate the lead time required to test will cause deadlines to seem artificial.
10. Do Have A Deployment Go Live Checklist
Don’t launch or have go live date without a checklist and a plan. Domain, Hosting, Server Security, Configurations, and Search Engine Optimizations, should all be considered before launch.
This article was first published by Cheyne Phillips on endertechnology.com