As we needed to create the new Homepage for the Mobile App, I suggested to go for a Design Sprint methodology. Low budget and small scope of the project led us to compress 1 week job in just 2 days.

The Team
1 UX (facilitator and Prototyper)
1 Product owner
2 Project manager (distributed: NICE + Bangalore)
3 Developer DEV (distributed: NICE + Bangalore)

Unpack - Understanding phase
With the team we unpacked all the information: many Business and Technical user stories were already in the backlog. This way we set the scope and we took useful notes as a team to reach the Design Sprint objective

In the second phase we sketched individually on paper, to generate new ideas and come with a bunch of proposal to discuss with the group.

After sketching, we presented all the ideas to the team and we used a structured critique to select the best ideas from the field of possibilities

We came over with multiple solutions to choose from and we couldn't prototype and test all of them. So with a tough voting session we decided the direction, based on a very collaborative approach

In a separate session I started the creation of a prototype: Axure, Photoshop and Invision. In just 1 day we came with a 'ready to test' interactive prototype.

Testing
At that time we couldn't go for a real testing session. Our design process wasn't complete.
That's why we just tested internally, knowing the limits of a totally biased audience. However, it was a good argument to bring on the table of the management, and the participation of the PO was key to let understand the importance of a testing session in the near future. 

This methodology was pretty unknown at that time in the team. Showing the output of our workshop to many colleagues was relevant to start a discussion on our design process, and bring some fresh air in the team. In 1 year we were able to switch from a Development Driven process to a new, more collaborative and inclusive way of working.