RP- Design-thinking-lab-work-using-Learning Launch.

Challenge   One of our clients envisioned to keep abreast with the latest changes in technology and wished to have  business transformation coupled with resolution of some of the lessons learnt and process changes  improve customer experience. As part of this journey the customer wanted to test the waters by taking  some of his applications, involving both legacy and third-party applications and explore the processes to  the methods of scrum project management. From the business perspective challenge is to improve the  workflow within the departments to increase overall online sales. The project has been time boxed to be  completed within 12 months based on the outcome the final project decision depends on.     Selection   The client has already invested in certain software and tools based on prior discussions with vendors  and experts. Even though the tools are in place we need to educate the team with necessary processes  and tool implementations so that we can launch the process to wider audience.  In short, the launch is  an experiment to test all the processes starting from Boxing the requirements, the design approach,  trainings involved and removing the kinks in the process so that the final deployment for all applications  will go through without major hinderances.    Application   To begin with, we have focused on the existing landscape of all applications and how the various  systems are interacting with each other. On analysis have realized that we have a backend system  talking to a middleware system to which all applications are talking to. In the launch the backend is the  one going to be changed and with this the changes trickle down to middleware and all applications.  Since the project is timeboxed and must explore all different tasks, project types and processes, have  identified a representative set of applications from the overall applications from different workstreams.  Once this initial assessment is made have structured the tasks within application projects to meet and  adopt to the scrum project management and arrived at a project timeline such as the various sprint  ceremonies, specific meetings, reviews in an effort to be agile. We had a buy in for this process with the  senior management as this is one of the requirements of the challenge. Following buy-in on the  approach had a training session with our team on the scrum project management. Then we had training  sessions cum workshops with he different workstream selected members to methodology and  structured the various tasks and processes following agile way. In the process we have created various  documents including governance, methodology, processes, workflows.  This has gained the confidence  and clarity from our business stakeholders one of the requirements we are satisfying and answered all  questions regarding prioritization of tasks, process changes and workflows and understanding of the  new process. The tasks of Business stakeholder and stakeholder buy-in was completed in about 4 weeks.    Insight   Applying the launch tool, based on the assumptions made and designed launches to test these  assumptions, our actual results varied from what we have anticipated for all the workstreams. While our  team was more open to the prioritization of tasks following the scrum methodology and tools used,  some of the workstreams due to their nature of work have to resort to different workflow methodology.   The team along with stakeholders have agreed to incorporate these in the future design launches.   There were additional learnings as to how many meetings were needed to follow up both horizontally  and vertical, some process and workflow changes and improvements were needed which have been

documented. These learnings are important and to be incorporated to have a successful roll out of the  entire project and part of design thinking.     Approach   The fact that the customer has already invested in certain software and tools and project being time  boxed makes the design thinking a bit more challenging As mentioned the team has to come up with  innovative ideas to perform the launch to help understand the intricacies in the launch. It is important to  review the learnings and incorporate them in future launch designs. Lessons learnt, progress made,  should be reflected in each o the launches from previous ones and reach the goals for a complete  solution.


RP- Design - thinking - lab - work - using - Learning Launch . Challenge One of our clients envisioned to keep abreast with the latest changes in technology and wished to have business transformation coupled with resolution of some of the lessons learnt and process changes improve customer experience . As part of this journey the customer wanted to test the waters by taking some of his applications , involving both legacy and third - party applications and explore the processes to the methods of scrum project management . From the business perspective challenge is to improve the workflow within the departments to increase overall online sales . The project has been time boxed to be completed within 12 months based on the outcome the final project decision depends on . Selection The client has already invested in certain software and tools based on prior discussions with vendors and experts . Even though the tools are in place we need to educate the team with necessary processes and tool implementations so that we can launch the process to wider audience . In short , the launch is an experiment to test all the processes starting from Boxing the requirements , the design approach , trainings involved and removing the kinks in the process so that the final deployment for all applications will go through without major hinderances . Application To begin with , we have focused on the existing landscape of all applications and how the various systems are interacting with each other . On analysis have realized that we have a backend system talking to a middleware system to which all applications are talking to . In the launch the backend is the one going to be changed and with this the changes trickle down to middleware and all applications . Since the project is timeboxed and must explore all different tasks , project types and processes , have identified a representative set of applications from the overall applications from different workstreams . Once this initial assessment is made have structured the tasks within application projects to meet and adopt to the scrum project management and arrived at a project timeline such as the various sprint ceremonies , specific meetings , reviews in an effort to be agile . We had a buy in for this process with the senior management as this is one of the requirements of the challenge . Following buy - in on the approach had a training session with our team on the scrum project management . Then we had training sessions cum workshops with he different workstream selected members to methodology and structured the various tasks and processes following agile way . In the process we have created various documents including governance , methodology , processes , workflows . This has gained the confidence and clarity from our business stakeholders one of the requirements we are satisfying and answered all questions regarding prioritization of tasks , process changes and workflows and understanding of the new process . The tasks of Business stakeholder and stakeholder buy - in was completed in about 4 weeks . Insight Applying the launch tool , based on the assumptions made and designed launches to test these assumptions , our actual results varied from what we have anticipated for all the workstreams . While our team was more open to the prioritization of tasks following the scrum methodology and tools used , some of the workstreams due to their nature of work have to resort to different workflow methodology . The team along with stakeholders have agreed to incorporate these in the future design launches . There were additional learnings as to how many meetings were needed to follow up both horizontally and vertical , some process and workflow changes and improvements were needed which have been documented . These learnings are important and to be incorporated to have a successful roll out of the entire project and part of design thinking . Approach The fact that the customer has already invested in certain software and tools and project being time boxed makes the design thinking a bit more challenging As mentioned the team has to come up with innovative ideas to perform the launch to help understand the intricacies in the launch . It is important to review the learnings and incorporate them in future launch designs . Lessons learnt , progress made , should be reflected in each o the launches from previous ones and reach the goals for a complete solution .