I have been using sumApp with Kumu for a couple years now. There are a lot of moving parts to keep track of when you build a project. The tendency is to dive right in ... and as you go you remember to do this and add that and what about those? How do you estimate your work-time if you can't even remember all the tasks? Here's a a first-draft diagram that might help. I needed it and so might you. Try it out and let me know what I missed. Or fork it and post your version. Much obliged! https://kumu.io/slimjimbest/sumapp-things#ssming-process/ssming-process-copy
In this morning's session Christine explained why we have to go back to the drawing board and start from square one with the much anticipated survey upgrade. Which means it will still be several months before we have a new survey tool and it won't look
Thank you to everyone who joined for this tech talk session. We are so appreciative that this Community of Practice is one that is willing to engage and get hands-on. This Tech Talk session introduces using Miro Boards with the group if you are additionally
This Community of Practice Tech Talk video explores the new Dual Elements feature in sumApp as it solves a bunch of problems related to mapping people AND organizations/networks/initiatives. What if you don't need all that robustness? Or what if you don't have the budget for sumApp's 2 Tier IV projects? We'll discuss the possible work-arounds and trade-offs to consider if you can't justify using Dual Elements. Links that were shared in this video/chat discussion: Approaches to Mapping People AND
Use this forum to ask questions, initiate discussions, and offer suggestions about DEALING WITH DATA. sumApp does everything it can to help get your data cleaned up & structured so that it works well with Kumu. But even so, data gets messy, and the way data flows from one context to another sometimes demands thought. If you're stuck or confused or just think it could be handled better - let's talk about that here!