Label: pattern

Content with label pattern in KM: Agile Software Release Strategies (See content from all spaces)
There are no related labels.

Page: Automate releases
every release has a large chance of error due to clumsy operators or bad documentation, releasing frequently becomes suicidal. Make sure that the release process open for a little human error as possible. First, make sure the documentation and routines are simple ...
Page: Customer by customer
Problem/Context In a Replacement project where the existing system is based around customer accounts. Solution Develop just enough features to be able to migrate a small number of customer accounts. Migrated accounts should be of the same type. More customers are migrated ...
Page: Duplicate input
Problem/Context In a replacement project the existing system handles a pipline of transactions. Solution Duplicate incoming transactions so that both the new and the existing system can handle them. Strengths Weaknesses
Page: Facilitate switching
Problem/Context Many of the patterns used in replacement projects lead to a transitional period where at least some user groups will use both the existing and the new system in parallel. In these cases users will appreciate any steps taken that make it easier for them ...
Page: Limited releases
Problem/Context The risk or cost of rolling out a release to the whole user group is large. Solution Identify a small group of users that can be used as pilot users. As few as 68 users can be representative for a whole user group. Deploy a release ...
Page: New orders
Problem/Context In a replacement project or enhancement project the existing system has a steady stream of new orders, requests, cases to be handled, etc (hereafter referred to as orders). Solution Develop enough features in the new system to support new orders of the simplest ...
Page: Partial history
Problem/Context In a replacement project the existing system contains large amounts of historical information. Much of this information is not in active use but must be available for reference. Solution Only migrate information that is actively used. Once the new system can handle ongoing ...
Page: Partition the workflow
pattern is usually used in combination with the Workflow by workflow pattern. The New orders pattern is also often relevant. Problem/Context The system being built contains one or more important workflows. A special case of this pattern is when the workflow plays out ...
Page: Product by product
Problem/Context In a replacement project or enhancement project where the existing system handles products of different types. Solution Create enough features in the first release to make it possible to migrate one product from the existing system to the new one. Later ...
Page: Replicated database
pattern has many similarities with the Synchronized database pattern. Problem/Context Solution Create migration scripts that at regular intervals retrieve data from the existing database and populate the new database. Any changes to the new database will be lost at this point in time ...