Smart Thinking for Better Outcome

In today's IT industry,  most of the projects follow Agile (SCRUM or KANBAN). During the course of the project mostly towards the tail end or in middle, there is a word that sounds like this "HARDENING" sprint. This is hard to be heard by business as this sprint will not produce a value added release. Rather it focuses on the stability of the app or course correction.  The What: Hardening sprint as said earlier will not take new requirements from the backlog, rather the story will be app stability or defects to be addressed. This is more or less an technical sprint without any architectural output. The desired output is a more stable working app. The Why There are the 3 major reasons for the "Hardening Sprint" to happen 1. More open defects The "Done" is "NOT Done". There are too many defects open at the given time. Functional and non-functional defects making the application less valued by business. 2. Course Correction Since, Ag...

The following are the steps to quickly ascertain the UX for the Mobile (can also apply for Web) From where or How the user will get to this screen What tasks the user can do on this screen How the user can cancel What will happen on cancel or where will be the the user taken to How many touches or clicks does it take to reach to this screen How many fields are selectable vs how many needs virtual keyboard (remember virtual keyboard distracts the user from the transaction) On successful completion what will happen or where will be the  user taken to Overall, remember to have the same pattern throughout the app so that users will need to learn once.