James Hea, FileMaker DevCon 2015
Change management is a critical component of IT project success, particularly within regulated environments. Businesses must implement effective processes to manage changes while complying with strict regulations. This extended guide explores the key aspects of change management from the perspective of FileMaker solutions, providing practical steps for implementation and ensuring compliance.
Menu
- Session Objectives
- Assessment in a Regulated Industry
- Why Does Change Management Matter?
- The Change Management Premise
- Change Management Steps
- Challenges and Strengths of Traditional Methods
- Best Practices for FileMaker Change Management
- Case Study: Managing FileMaker in a Financial Institution
- Key Takeaways
Session Objectives
The primary goal of this session is to provide a deep dive into change management in a regulated industry. Specifically, it focuses on how FileMaker can support these processes by:
- Ensuring scalability, whether managing small projects or enterprise systems.
- Maintaining compliance with regulations.
- Managing reputational risks through efficient change processes.
This session equips you with the knowledge to implement robust change management strategies for FileMaker solutions.
Assessment in a Regulated Industry
In regulated industries, documentation and tracking are not just recommended—they are mandatory. Regular audits, system failures, and proper approvals make it essential to create detailed audit trails, especially when changes are made to FileMaker systems.
Key areas to focus on include:
- Audits: Required both internally and externally to ensure compliance with industry standards.
- Tracking and Approvals: Logging and approving all change requests.
- System Failures: Preventing failures that can lead to financial or reputational damage.
Why Does Change Management Matter?
In regulated environments, the impact of poorly managed changes can be severe, leading to non-compliance, fines, or reputational damage. Factors that make change management crucial include:
- Industry Complexity: Larger organizations often require more complex approval processes.
- Security Concerns: Ensuring security protocols remain intact during changes.
- Reputation: Poorly managed changes can result in audit findings or client dissatisfaction.
The Change Management Premise
In an effective change management process, each stakeholder’s role is clearly defined:
- Business owns the data: Data integrity is maintained under business control.
- Business owns the process: Any process change must be approved by the business team.
- IT owns the application: IT manages the application but requires approval for changes.
- Business tests changes: Testing is a joint effort between business and IT, although resources may be limited.
Change Management Steps
Managing changes in a FileMaker solution requires a structured process. These are the key steps:
Initial Request
The change management process starts with an initial request. This could be a request for an enhancement, bug fix, or feature modification. At this stage, preliminary analysis and interviews are conducted to gather requirements.
Key activities:
- Interviews: Understanding user needs.
- Gatekeeper Approval: Gaining approval from management before proceeding.
- Requirements Gathering: Collecting both functional and technical specifications.
Change Request
Once the initial request is approved, the design and testing phases begin. This phase ensures the proposed changes are implemented correctly without introducing new issues.
Key activities:
- System Design Specifications: Detailed system architecture documentation.
- Testing: Multiple layers of testing, including unit testing and user acceptance.
Implementation
Once the changes pass testing, they are ready for deployment. A detailed implementation plan ensures a smooth transition to production.
Key activities:
- Release Notes: Documenting changes and communicating them to stakeholders.
- Deployment: Migrating the changes to the live system and ensuring operational continuity.
Support and Bug Fixes
Ongoing support and bug fixes ensure that any issues encountered after implementation are addressed promptly. This stage includes:
- Bug Fixes: Addressing newly discovered bugs or issues with third-party integrations.
- System Upgrades: Ensuring compatibility with new FileMaker versions or system updates.
Challenges and Strengths of Traditional Methods
Challenges
Traditional change management processes, often following the waterfall model, are not without drawbacks:
- Rigid: The process may be inflexible, making it hard to adapt to fast-changing business needs.
- Waterfall: The sequential nature of waterfall approaches can lead to delays if one stage is held up.
- Cost: The high cost of traditional processes, particularly for small organizations, can be a concern.
Strengths
Despite these challenges, traditional methods have several strengths:
- Audit Compliance: Detailed documentation and approvals provide the necessary compliance for audits.
- Disaster Recovery: Proper change management ensures business continuity and recovery from failures.
- Training and Support: These methods provide thorough documentation and ensure teams are well-prepared for any changes.
Best Practices for FileMaker Change Management
To modernize your change management process for FileMaker, consider adopting the following best practices:
- Continuous Integration/Continuous Deployment (CI/CD): CI/CD ensures incremental testing and deployment of changes.
- Version Control: Use version control tools like Git to track FileMaker code changes.
- Automated Testing: Automating tests can catch issues early and reduce time spent on manual testing.
- User Training: Thorough user training ensures smooth adoption of new systems or changes.
Case Study: Managing FileMaker in a Financial Institution
In a financial institution, change management takes on greater importance due to strict compliance requirements. A typical process involves:
- Compliance-Driven Changes: Regulatory updates drive the need for system changes.
- Audit Trails: Every change is documented to ensure compliance with financial regulations.
- Collaborative Process: IT and business stakeholders work closely together to ensure changes meet both compliance and business needs.
Key Takeaways
Change management is vital for maintaining compliance, security, and efficiency in regulated environments. By adopting best practices like CI/CD, automated testing, and strong documentation, organizations can enhance their FileMaker change management processes while meeting the demands of audits and regulatory requirements.
FileMaker DevCon 2015: Change Management in a Regulated Environment – James Hea
For additional resources, check out the session updates.
