After discussing the requirements, expectations, and technology that fits their business, you begin your work. Since we develop software iteratively, the customer expects to see progress and, more importantly, to understand it. 

What you need to do as a software developer now is to: 

• Demonstrate the new code 
• Demonstrate what you fixed or improved so far 
• Demonstrate how you are taking into account their input 
• Manage their expectations 

Frequently, it is not enough to just talk about what you did while sharing your screen during a conference call. It is always good to bring more material you think the customer will find helpful to the meeting. Here is what potentially helps the customer understand how much input you had:

• A table of outstanding vs. completed tasks (also, you can include task completion percentages or color code your table)
• A visual comparison of the current sprint vs. the previous one
• If you are using a project management tool, extract the completed tickets
• A timeline for the present or the upcoming sprint 
• An estimate of how much time you spent working on the problem
• If the problem is complex, a mind map helps visualise the scope

You can dedicate 3 minutes to mention the above points at the beginning of the demo. If you are working with a project manager or within a development team, you can suggest sending a weekly update that includes a document of some or all of the above points. If you are working alone, sending a detailed update to the customer is always helpful.

Finally, always have a short script – write down the exact talking points you will mention in your demo. This helps put your thoughts and ideas on a piece of paper and practice how impactful your demo can be. While thinking about your demo script, also try to anticipate the questions from your audience. If possible, you can also address some of the questions in your demo.