In order for the integrations team to have consistent planned work available to bring into milestones, we strive to have a healthy funnel of incoming work. We do this in a few ways:
Prior to scheduling an engineering task into a milestone, we need to have a good understanding of the problem, the ask, and well-defined requirements. This assists us to design a solution that meets your core business needs and does that in a reliable way. This also has a secondary benefit which is that we can properly automate the testing of integrations so that they are easy for us to support and maintain. This allows our team to stay lean and flexible so that we aren't bogged down in support activities.
We may ask you for any of the following documentation, designs, and information to help us plan your project:
Note: We don't always have spare Project Management or BSA resources to devote to your project so we may ask for you to assist us in owning in these activities.
We run 1 month long milestones (sprints) which start on the first Tuesday of the month. Our milestone calendar follows a repeating pattern of predictably scheduled rituals:
|Ritual||Week before milestone||Week 1||Week 2||Week 3||Week 4|
|Planning||X (multiple sessions)|
|Kickoff||X (first day)|
|Retrospective||X (last day)|
For integrations we have built we have logs, monitoring and alerts which automatically trigger when an issue arises in an integration or automation. We track bugs and incidents in our Integrations Work Tracker and on our Milestone Board.
If you need to report a bug or incident to us, please do so using the bug report template listed below.
For maintenance and enhancement of existing integrations please submit an issue using the correct template below.
To learn about our processes please visit the sdlc page
Pick one of the below to be directed to the correct issue template
Once you have reached out to us, we will help you in determining the size of your project, and subsequently the types of planning assets and activities that we'll require to help things run smoothly and make your project a success.
|Small (S)||- Switch to sending preferred names to existing EdCast integration via the API||TBD|
|Medium (M)||- Navex Global integration (upload daily list of users to FTP server)||TBD|
|Large (L)||- Zuora to Netsuite Integration||TBD|
|Extra Large (XL)||- Switch out a core system and rebuild all integrations||- Break this project down into size L or smaller projects|