Knowledge Release Process

Planning

Before kickoff, stakeholders prioritize tasks.

Provide time before kickoff for IKEs to review tickets for commitment.

Beginning of every month.

Get buy-in and commitment from IKEs that the tickets selected are doable for the month.

Provide IKEs with defined dates for each phase(i.e. Testing, RC, and Release)

Provide stakeholders visibility in what will be coming out in the next release

Approximately 3 weeks..Depends on the month.

Research, Develop, and Test

More to follow on another email.

Scripts and rules should be reviewed and ready to be merged into staging by this date for the release.

Will not longer require retesting of most scripts and rules.

We are planning to build more automation testing internally

At end of month

Two weeks of beta testing on customer site.

If any issues occurs with tickets, will need IKEs to fix.

During this time, will kickoff the next release at the begging of the month.

If all goes well with beta testing, do a general release.

Goal to release once a month. (after first release)