Four groups, totally appr. 30 people Active and enthusiastic people working together Many findings contribute to the product management plan However, numerous questions were raised The results function as the input to today’s workshop Theme 1: role descriptions Theme 2: consortium rules Theme 3: financing and ownership Theme 4: risk management
could be discussed but are not limited to: Which roles are needed? What is the interest/motivation of each role? What is the highest authority/group in consortium that makes the decisions about the features of Pilviväylä SW? What kind of alternatives there are? What are the responsibilities of the consortium. What is the role of steering group/support group? Roadmaps, visions? Who is Product Manager? Tasks? Who is Coordinator (openness)? Tasks? What is the role of the ministry (OKM)? Roles and responsibilities of developer community? Roles and responsibilities of the development core team? Role of schools and teachers in consortium? Prioritization of new requirements and change requests: who decides?
could be discussed but are not limited to: How to propose new ideas/features? Users (schools, etc.)? Developers: GitHub issues? How to handle communication (consortium internal/external)? Linkedin? Facebook?, … How the changes to Pilviväylä will be handled (how, who)? Collecting ideas/proposals, analysing, change request, decision, implementation, acceptance to production? What are the documentation requirements of Pilviväylä? What needs to be documented to enable development? How to handle version management? How to analyse/integrate external contributions/components? Consortium terms & conditions: agreement, entering/leaving consortium, …
that could be discussed but are not limited to: Owner of Pilviväylä in different life cycle phases: pilot phase – owner = ministry, production phase – owner = ”commercial actor”, internationalisation phase – owner = ”commercial actor” ? The role of EduCloud consortium as an owner? How to finance: the development of Pilviväylä maintenance product management activities and roles (product mgr, coordinator, operation of consortium, …) => e.g. Establishing Pilviväylä and the consortium (2014)(subscription fee) => 2015: Pilviväylä will be financed by the customers (who?) of the Pilviväylä => (it might take a while until the operation ”pays itself”). How to allocate expences between partners (management work, maintenence, future development of Pilviväylä)? How to help the deployment and usage of Pilviväylä in municipalities? E.g. municipalities can get ”seed money” (siemenraha) or service vouchers (palveluseteli) to acquire educational material from Bazaar/Pilviväylä (are there other possibilities). How to follow where the money has gone? Business models of the consortium?
could be discussed but are not limited to: Definition of the product/service (Pilviväylä/EduCloud) under development, who is the customer? Purchasing process: how schools/users buy material? If ending with Bazaar owned by the OKM, what is the business model? Open standards, APIs and interfaces? Finnish X-Road? Information security in Pilviväylä? How to involve parents to consortium?