Whenever the main problem (i.e. attendance) isn't being the focus, it's a good indication of scope creep.
Negotiate, get back to the main focus, don't agree to things on the spot, ensure buy-in is formal (formal being adding the feature into backlog and seeing how/where it fits in with sprint planning), stick to items in the current sprint backlog
Google turns up no results.
Use teammates as resources (assist in explaining), alternative technologies (different plugin, etc)
Magic solution, when you notice someone is super excited for a given technology. When a suggested technology doesn't actually map to a use case
Check to see if the goals of using the technology match any of the user stories or use cases (before investing heavily into the technology), after the fact prune all technologies to see if there are redundancies
Not communicating goals and tasks well, identified by consistently missed targets
Ensure that changes (pertaining to communication) is bought in by everyone and ensure consistency throughout the period of the project. AND ask questions whenever something is unclear
A lot of time learning (not contributing to development)
Pair programming, an expert in each problem domain
Approaching milestone and haven't reached the target (the goals planned/sprint committment)
Intermittent planning (keeping our velocity up to date with how well we perform at that current time). Make sure tasks are small and manageable (tasks are broken into "doable" blocks of time, e.g. 2 hours instead of 2 weeks duration)
The wrong person doing the wrong task, tasks are getting done because no one knows what they're supposed to be doing ("I thought you were going to do it")
Make sure that during sprint planning process, individuals are being assigned specific tasks (as they are added to the sprint, someone is assigned to them). There will be a regular check-in giving updates of what is being done by each individual (to be completed at the weekly meeting)
Unrealistic sense of status (if things seem to be coming too good at the end of each sprint). The customer doesn't seem happy with progress. Ask questions like "where is this?" "what is the status of this"
Make sure that tasks assigned ourselves are completed, make sure customer's needs are met. Transparency with what you're doing (report on Asana)
Unable to hold regular meetings. Poor meeting attendance.
Communicate, give notice, complete task before will be absent or work to give to someone else, remote meetings
Your data is not there anymore
Redundancy, backups, version control
Difficulty staying on topic, poor productivity, not focusing on the main task at hand
Set concrete goals for each day (agenda) with deadlines, to know if meeting tasks
Conflicts putting units of work (design, code, ideas, etc) together
Integrate often and plan integrations ahead time. Plan APIs and notify each other of changes to open APIs/designs
Not knowing how to use a technology or tool, not being able to get the tool onto machine.
When making installations of software, outline the steps exactly how they should be completed and the order to complete them in
The technology doesn't fit the use case. Trying to make the requirements/project work with (fit) the technology
Choose technology based on actual ability to fulfill the use case. Go with technology that has been shown to work in similar environments
Silence. Showing up to meetings late. Lack enthusiasm
Candy & burritos. Make meetings fun. Assume you're developing for yourself (make it your own project)