We are currently in the early phases of developing a web application for a client. We have regular sprint demo's during which we take the client through the new features and changes from the last sprint. We also want to increase our deployment rate, so that new updates and changes can be available to the client earlier for feedback - we may consider getting this list generated automatically. We also need this to be as lightweight as possible with minimal technical effort and impact.
I am looking at modifying our development web application to include a 'What's new' and a 'What's changed' section with the intention that these have a very strong 'call to action' feeling about them without being intrusive to the normal operations of the site. I want to communicate changes/new features really quickly to users in the event they missed my email.
I have narrowed my options to the following approaches:
- On login, a modal window is shown to the user providing them the option to view these two links. They can dismiss the modal and continue as normal.
- Include links with the top menu or sticky footer.
The linked pages will have similar styling as the rest of the web application and will present a list of changes etc in chronological order (newest first).
My user base at the moment is limited to the client who I rate as competent web users. In addition,I have yet to think of a way to make it clear these new pages are temporary and will not be part of the final product.
Given the requirements and objectives above
- Are there other techniques that can achieve similar results?
- Which technique will be more suitable?
I have looked at Adding a new feature to an existing website and I am not personally inclined to this approach - but will keep it in mind.