The Custom Business Software Show With Qubisoft

In this episode you’ll hear our thoughts on:

• What the traditional approach to custom software development and its costs are
• Why clients experience frustration with hidden charges and budget limitations
• When clients face difficulty in understanding the costs of custom software
• Why fixed price important for clients to manage risks
• What the negative consequences of paying for software development by the hour are
• What factors are considered in project cost estimation
• What the timeframe for project completion in custom software development is
• What exclusions and uncertainties are in the project scope
• What concerns with the traditional custom software development process are
• How the traditional software development process involves tapping into a budget pool for funding
• What the uncertainty with the traditional software development process in terms of project completion and cost is
• What the benefits of fixed-price contracts for consumers are
• What the pros and cons of traditional versus fixed-price contracts are
• How the comparison with fixed-price contracts in the building industry helps explain custom software development
• What cost-plus contracts and how they compare to fixed-price contracts

So, listen here as we discuss these!

If you like what was on here and want more, go to https://www.qubisoft.com.au/

In this episode you’ll hear our thoughts on:

Focusing on the full project lifecycle with an Agile method

• Providing best practice guidance for on-time and on-budget delivery
• Adhering to its 8 principles
• Meeting with the client to comprehend project objectives
• Conducting a workshop to identify high-level features and screens necessary
• Examining business constraints and processes to determine how the solution can enhance the business
• Diving deep to uncover any risks or complexity
• Calculating the entire project timeline
• Breaking down the large time box into smaller “time boxes” for each feature
• Progressing with development, testing, and deployment iteratively
• Achieving 80% of the value with 20% of the effort
• Delaying adding polish until the application is in a workable state
• Enabling early delivery of value to the business
• Employing a visual tool to show work at various stages of the process
• Representing tasks with requirements and time estimates
• Encouraging clients and stakeholders to be actively involved in the process
• Continuing the process after the "time box" of work is completed
• Adding new mini "time boxes" and continuing the process
• Moving through the requirements gathering, development, testing, and deployment phases

So, listen here as we discuss these!

If you like what was on here and want more, go to https://www.qubisoft.com.au/

In this episode you’ll hear our thoughts on:

• Inquiries about software
• Advertisements for off-the-shelf software
• Custom software fitting specific needs
• Requirements gathering and design process for building software
• Quoting workshop to provide cost and timeframe estimates
• Development, testing, alteration, deployment, and documentation time
• Cost of time and number of people involved in a software project
• Profit margin and expenses for licensing and tools
• Prototyping and research for unique software projects
• Error handling and catering to various use cases
• Retry mechanisms for failed data input
• User experience and satisfaction with the software
• Ongoing maintenance and updates for software
• Outsourcing software development to companies using older technologies and languages
• Difficulty in finding developers to maintain older technology
• Lack of protection under Australian Consumer Law when outsourcing
• Overseas companies posing as Australian companies
• Lack of access to source code and accounts when using overseas development companies
• Extra cost to rebuild and reverse engineer documentation when using overseas development companies
• Importance of clients having access to accounts, source code, and documentation for software development projects
• Use of Agile and Scrum methodologies and Kanban boards in software development projects
• Factors that can impact the cost of a software development project, including the length of the project, number of developers, and profit margin of the development company
• The importance of ongoing maintenance and updates for software
• Use of on-demand technical roles such as project managers, CTOs, and team leads
• Higher wage costs for in-house senior developers compared to using on-demand support
• Lack of support for software developed by other companies
• Ability to maintain and support existing software without having developed it
• Skills needed to work with unfamiliar code and software
• Ad hoc problem-solving and lack of fixed procedures for supporting custom software
• Ability to improve and document existing software, and build relationships with clients
• And more!

So, listen here as we discuss these!

If you like what was on here and want more, go to https://www.qubisoft.com.au/