Type of user: The type of user is the broad category that this user falls into. Consider who is using your product, and the different tasks those groups need to achieve. You might have end users who only need access to the user interface, administrators who need access to all the functionality your system offers, and developers who need to be able to access the source code. Classifying users in this way can also help you with setting up security and access measures, by asserting who can access which part of your interface, settings, and back end.
Persona: Personas are a good way of understanding each type of user you have. Personas are fictional characters who represent each user type, you can give them a name, a photo, and write about their typical day and usage in order to better understand how your users interact with your system.
Environment: The environment is the location that your user is interacting with your system. It could be at an office, on a work site, in transit (perhaps on public transport, or an aeroplane), from their home, or any number of other locations. This can greatly impact how you deliver information to them, based on things like lighting, ambient noise, whether they'll have access to data services, or be relying on using a small screen.
Do something: This is the crux of the task: what do they need to do? This will usually be something like creating accounts, processing sales, recording or retrieving information from a database, or any number of other actions that your users will need to do.
Platform: Platform refers to the type of technology your user is using to access your system to do this task. It could be a Windows desktop, an Android mobile application, or a Mac laptop, for example.
Reason for task: Why does your user want to do this task? In many cases this is straightforward (it's pretty obvious why someone might want to create an account), but in many cases this can give a good insight into user motivation, which can help you provide a better solution. So if users want to print out a customer list, for example, is it because they need to carry it with them, or because it's hard to read on their screen? Perhaps the solution isn't to develop a system for printing, but to improve the user experience of the customer list screen.
Achieve user goal: This final statement is used to align your tasks with your overarching goals, and can help with task prioritisation.