Communication in Teams from the Developer Point of View
•Transferir como PPTX, PDF•
0 gostou•612 visualizações
Bridging communications gaps in talking to developers about xAPI.
Recomendados
Mais conteúdo relacionado
Mais de Aaron Silvers
Mais de Aaron Silvers (20)
Último
Último (20)
Communication in Teams from the Developer Point of View
- 1. communication in teams ● Project ● Team Members ● Different Communication Styles ● Assumptions ● Cross Training from the developer point-of-view
- 3. Who do we need to communicate with? The Team
- 4. How should we communicate?How do we communicate
Notas do Editor
- Introduction: who am I. 17 year learning technology career LMS design and build LCMS design and build CMS design and build Structured content expert Learning technology consultant This session is about: Not so much the project, although we have to start there It’s about the communication in the team Developing learning systems that leverage xAPI technology can ultimately change how we communicate with our team. It changes the language that we need to use and it also changes how EVERY team member has to think to get the best results No longer are we limited by LMS gathering data, we can expose more of the learning and extend data gathering beyond the learning
- In the far past we build out modules Rapid authoring made that less important, we started to think about systems. We still only dealt with the digitally distributed learning assets, a PART of a learning system Present or considered future: We now have an opportunity to impact the whole curriculum and even beyond it, anywhere learning experiences occur We have new challenges We suddenly have fewer limits, but there are so few limits now, that we are challenged by the limitations of creativity We have been bound so long that we no longer have a taste for that true freedom This applies to developers and system designers as well as every other member of a team
- Project teams have managers, developers, designers, all types of skills, but I want to focus on the specific changes in the roles of a developer and an instructional systems designer (ID) Teams need to talk. They need to communicate with one and other and to do that, they need to find a common language to use that each of our team members can understand. There are many opportunities that could be over-looked if we don't Developers need to talk to Instructional Designers, we both have a modified role when developing these learning systems Communication in the modern team requires a different level of understanding that it has in the past. Developers are a more integrated part of a whole learning system which we may know little about and IDs are being introduced to recording experiences in a way that has never been done before.
- We need to eliminate confusion and frustration. At my shop we had a common language breakdown between these 2 groups. IDs needed to understand xAPI and asked relevant and reasonable questions to back-fill a preceived lack of understanding. Those questions were met with short and vauge answers. “what does xAPI look like” = “it doesn’t look like anything, it’s technogoloy” . The “you wouldn’t understand” mentality at it’s best. We had to shift to a “you need to understand” mentailty before we could proceed. Developers need to start conversations about what IDs need to know and conversations about they need from the IDs. We all communicate in different ways but we need to find a common ground. Developers need to help IDs to understand the technology, this won’t be easy, but it will pay off. Developers need IDs to identify opportunities for meaningful data to be gathered. Developers cannot dismiss questions or give vague answers, we need our developers to be leaders in providing specific and detialed answers to specific questions and continuously tying the message back to the overarching objective of the project. Devs need to train IDs on xAPI and how the technology can assist the system to achieve the goal. In the same thought process, IDs need to train Devs on learning systems, the design and the human interaction.
- We need to eliminate confusion and frustration. At my shop we had a common language breakdown between these 2 groups. IDs needed to understand xAPI and asked relevant questions. Developers need to start conversations about what IDs need and conversations about they need from the IDs. We communicate in different ways. Developers need to help IDs to understand the technology, this won’t be easy, but it will pay off. Developers need IDs to identify opportunities for meaningful data to be gathered. Developers cannot dismiss questions or give vague answers, we need our developers to be leaders in providing specific answers to specific questions and continuously tying the message back to the overarching objective of the project. Devs need to train IDs on xAPI and how the technology can assist a system. IDs need to train Devs on learning systems, the design and the human interaction.
- Devs need to train IDs on xAPI and how the technology can assist a system. IDs need to train Devs on learning systems, the design and the human interaction. Devs need to slow down and really inform IDs on what the technology will be enabling. IDs will be called upon to inform devs of all the components of a learning system. We need to ultimately work together to identify the opportunities (ID) and methods (Dev) to gather deep and meaningful learning experience data.
- We cannot assume that an ID is thinking the same way as a developer and vise versa. We cannot assume that they know how things could be "hacked" to work with new technology, re-designed to work differently, or acquired to bridge a gap. They may… but they have not been traditionally exposed to that. We also can’t assume that developers know everything about learning systems… they traditionally have only had deep and meaningful exposure with a relatively small part of those systems IDs can be a valuable asset when exposing parts of the learnding system that can be opportunities to gather more meaning experience data. We need to ensure that they are armed with the knowledge to identify those opportunities and/or create opportunities in a system.
- We all need to be IDs and attempt to change the IDs mindset on technology challenges. Include some quotes: Common in my shop: General: " I never would have thought that we could do that, like, I never would have even considered that" Specific: "But it's a classroom, it's not online, we can't get data" Important to take the time to inform about why things are now different. Take the time to use analogy, and story-telling with examples to really gel these abstract concepts of data gathering. Emphasize the importance of the data, the types of data and waypoints along the journey that require data gathering. And always loop back to the overarching objective. But don’t let me get away with making IDs out to be non-tech savvy people that won’t think about xAPI as a massive opportunity to gather never before gathered data. The developers may believe that IDs need to learn quite a lot in-order for learning design to harness the true potential of xAPI. But, I think the developer now needs to learn quite a lot about learning design, interactions, and assessment of learning, the journey after training, in-order better design xAPI recipes that lead to meaningful results. The developer needs to learn the soft side of human computer interaction and how systems are interacted with. They will need to understand not just what the massive collection of data points means but also what the lack of certain data could mean. That could be functionality gaps, a lack of edge-case testing or poor interface design.
- at the end of the day… Change can start with one agent. One champion of a new way of thinking and a new set of meaningful results to acquire. BUT, it takes a team to realize that change and implement the new technology. There will be challenges, but the journey will be a very meaningful experience and an excellent opportunity for growth. growth as a solidified team and growth as individuals in the modern learning design landscape. This will provide the best foundation for a successful and rewarding implementation of xAPI in a learning system. Thank you.