Successful legacy system replacement hinges on thorough requirements discovery, documentation of undocumented business rules, and effective communication with offshore teams.
About:
Frank Ray, owner of Better Software UK, is a former Microsoft developer and author focused on improving agile software development.
Website:
Specializations:
Interests:
Subscribe to RSS:
Effective business analysis relies on human skills and capabilities, not on expensive software tools, which often fail to address underlying issues in requirements gathering.
A nine-month analysis of over 2,000 incidents at a financial services firm led to the development of an AI tool that transformed their approach to quality improvement.
Understanding the specific needs and context is crucial before hiring a Business Analyst to address communication and requirement issues in software development.
Effective business analysis hinges on clear communication, understanding context, and defining outcomes, rather than merely following prescribed methods.
The post reveals that offshore development delays stem from organizational dysfunction rather than unclear requirements, emphasizing the need for better communication and test automation.
Effective software requirements are crucial for agile teams, providing necessary context and clarity to enable informed decision-making and avoid development blockers.
Identifying and addressing the signs of a struggling development team is crucial for recovery, focusing on systemic issues rather than individual incompetence.
Successful offshore development relies on clear requirements, effective communication, and adapting processes to fit remote teams' realities, rather than imposing local practices.
Early engagement of an independent expert in IT disputes clarifies responsibilities and can prevent costly litigation by providing objective assessments of both parties' contributions.
A comprehensive guide for solicitors on effectively engaging software engineering experts in IT disputes, focusing on timing, evidence gathering, and strategic legal advice.
Understanding the reasons behind software project failures requires a technical assessment to clarify accountability between clients and suppliers, as illustrated by a detailed case study.
Developing a safe AI emotional regulation coach requires careful oversight, personalized responses, and an understanding of the unique challenges faced by vulnerable users.
The Business Analyst role is collapsing as AI and technology blur the lines between software development roles, demanding greater expertise and adaptability.
Integrating AI agents has transformed the author's work as a Business Analyst and Software Developer, enhancing productivity and emotional regulation while evolving their professional roles.
Choosing between a contract or permanent business analyst depends on project needs, budget, and the importance of knowledge retention and team integration.
Refinement sessions transformed Damien's chaotic planning meetings into efficient, focused discussions, significantly improving team dynamics and morale.
Technical debt accumulates from rushed coding and poor practices, leading to inefficiencies, and requires deliberate management to prevent long-term costs.
A checklist of anti-patterns reveals how to create a dysfunctional software development team, suggesting that recognizing these issues may indicate it's time to leave the workplace.
Understanding and documenting both functional and non-functional requirements is essential for developing software that is not only functional but also reliable and user-friendly.
This blog post presents a free tool for evaluating software development standards, aimed at businesses and legal professionals involved in IT disputes.
The author describes their experience with autism and the creation of 'Anna', an AI emotional regulation coach that aids in managing emotional dysregulation and trauma.
The author draws parallels between car restoration and software development, advocating for a craft mindset that prioritizes quality and community over mere transactional work.
User stories and use cases are distinct tools for capturing requirements, with user stories focusing on user needs and use cases detailing system interactions.