FAST TRACK RELEASE MANAGEMENT (3 to 4 months)

REQUIREMENTS GATHERING, DEVELOPMENT & TESTING IN AGILE -
[NEW PRODUCT]

Starting from Iteration 1 and developing till the final iteration.

As the image above shows, the project development is done from iteration 1 till final iteration 8.

Each time a new layer of new feature/functionality is added to the existing project.

Requirements, development and testing all are iteratively done and in end, collective release advice is given.

1. Plan Release - 

Plan a small release every 3 to 4 months. It is wiser to develop small features, test them and release them.
keep new development in control and use a small steps approach.
when developing small features/functionalities then we have more control. We can use the client feedback to further develop in next iterations. Chances of making mistakes are less. And if any problems are noticed, then its always easier to manage a small release.

Delivering a large functionality is always a risk in long run for stakeholders.

Start in 2-Jan 2018 Week 1, 2: 
Tasks:
preparation and plan.

2. Gather Requirements - 

1. keep the cycle of requirements gathering Short.
Gather requirements in a time-boxed manner. This means that you decide a specific number of days for requirements gathering and do not extend them.

Tip1: Make use of requirements management tools like  Rational Doors.
https://en.wikipedia.org/wiki/Rational_DOORS


Tip2: Include the client in the team and ask to perform the task of requirement gathering on a high level. assign Business analysts and Functional analysts under him and ask to finely define the high-level requirements.

Example Case 1

Start in 15-Jan 2018 Week 3, 4: 
Tasks:

• preparation, interview client 
• Collect requirements, 
• draft and propose version.

3. Review requirements - 

Start the requirements review phase. This is a mandatory phase.
  where the team reviews the requirements in a formal way and notes down the comments or questions and answers.
  sometimes a rework is required and also some extra details are required. So these can be collected as part of the review phase.

For example - 3 days for review and 2 days for any rework or changes.
This way the stakeholders/managers get the assurance that the requirements have been read and understood by the team and are ready as the basis for the development. Now the requirements collection is complete.
Tip: Use the standard template for the review process.

Who is involved in the Review process;
1. Software architect
2. Software lead developer
3. Test Manager/Test coordinator/Test Lead.

Example Case 1

Start in 29-Jan 2018 Week 5, 6: 
Tasks:

present requirements,
Collect feedback/questions.

update the draft and create a proposed version.

Develop - 

Once the requirements are reviewed and finalized. Now its time to start development. Using the agile way for development split the set of requirements into small user stories and distribute them over the span of project development time.  

It is important that at end of each sprint the feature developed can be verified by the test department.

This verification is essential in order to set the user story on Done. 

We cannot put the status of a user story on done, until and unless the user story is tested and no major bugs are open.
This process step will ensure the stakeholders that steady progress is made and no open ends are left.

Example Case 1

Start in 11-Feb 2018 Week 7, 8,9,10,11: 
Tasks:

• split requirements into small user stories.
• plan, assign and develop, 
• unit test.
• deploy software for testing.

Code Review - 

Often the stakeholders are left with some risks and lack of assurance. Some common questions popping in minds are like:

• Is the project code suitable for future enhancements?
• Is the architecture future proof?
• Are we able to quickly adapt the solution when a new change request or a new feature demand is raised?
• Assurance that we are not making a house of cards.

Example Case 1

Start in 04-March 2018 Week 10,11: 
Tasks:

preparation, interview client 

Collect requirements, 

draft and propose version.

Test & Retest - 

Example Case 1
Start in 18-March 2018 Week 7, 8,9

Tasks:
Create test plan, test cases.

Prepare test data,

Start in 18-March 2018 Week 10,11,12: 

Tasks:

• Automate tests where possible, execute tests - manual and automated.
• Generate test report
• Execute Factory acceptance tests FAT and Retest+Reruns, bug fix tests.
• Execute Integrated Factory Acceptance tests E2E,
• Generate test report, 
• Give internal release advice for starting UAT.

UAT & Release.

Example Case 1

Start in 26-March 2018 Week 12: 
Tasks:
Prepare tests,
Execute tests with client,
collect feedback. (replan if needed)
create change requests or bugs. define strategy and acceptance of these issues.
plan effort - if minor development include in release.
                  - if major development include in next version of release.. 
Give Final release advice.

Software Released on 1-April 2018