Community capacity building and process improvements workshop
•Download as PPTX, PDF•
1 like•548 views
This document discusses community capacity building and process improvements for statistical information systems. It outlines steps to success, including identifying prerequisites without early restrictions, communicating openly, and providing constructive feedback. Development scenarios are presented, such as developing isolated plugins or new tools using existing web services. The document also discusses secondments from other organizations and process improvements for 2012, like test-driven requirements and unit testing.
Recommended
Recommended
More Related Content
Similar to Community capacity building and process improvements workshop
Similar to Community capacity building and process improvements workshop (20)
More from Jonathan Challener
More from Jonathan Challener (7)
Recently uploaded
Recently uploaded (20)
Community capacity building and process improvements workshop
- 1. Community capacity building and process improvements by Jonathan Challener OECD’s Statistical Information System Collaboration Community (SIS-CC) Workshop Paris, France 12-14 March 2012
- 2. Success is not one shining light
- 6. The ideal capacity levels
- 15. Avoid too many early restrictions Identifying the prerequisites (2)
- 16. Communicate openly Provide constructive feedback Identifying the prerequisites (3)
- 18. Development scenarios (2) Develop isolated plug-in Develop new tool using existing Web Service
- 19. Development scenarios (3) Add method to existing WS Add new features to core components
- 21. Development scenarios (5) 1. Develop isolated plug-in 2. Develop new tool using existing WS 3. Add method to existing WS 4. Add new features to core components
- 22. Development scenarios (6) Developing core components
- 24. Secondments (2)
- 25. Development process improvements New branching and merging policy Naming conventions Source control organisation Gated Check-in “Unbreakable Build” Force check-ins to be associated to work items Verify that the code checked-in compiles Basic Code Analysis rules
- 26. 2012 process improvements Test driven requirements Stronger acceptance criteria Unit tests: 100% coverage new developments 20% existing Automated UI tests Further code analysis 1st set of security rules Peer reviews Performance indicators Q1 Q2 Q3 Q4
- 27. So how is capacity building working in a real scenario…
Editor's Notes
- So what are the steps we are taking for a successful collaboration community
- and how are we increasing the community capacity
- to a level that fulfils the our potential
- So, why do we need to increase capacity?
- For one to reduce the heavy support burden on acentral team
- Build a team philosophy across all collaborating partners
- Understand how we work by sharing experiences, knowledge and best practices
- Enable innovation
- and in turn allow for co-developing state-of-the-art StatisticalInformation System
- First we identified the prerequisites for co-developing and building a successful community
- A sure way to stop collaboration from evolving is too many restrictions which will also stifle potential innovation
- Communication is as with most scenarios key and by being open and honest will provide the transparency to encourage growth within the collaboration
- Then we identify the development scenarios
- We categorised themby their level of complexity starting with the simplest
- and build on the complexity
- until we reach the core components
- Why categorise?If we take the less complex scenarios these can be undertaken from within a collaborating partners own organisation by those already with a good level of knowledge and skills in the .Stat solution.
- However, to undertake the developing of core components in the first instance has only proven to be successful through placement of a staff member in the OECD .Stat team.
- So far secondments have taken place with 4 different organisations and each one of these has proved to build capacity and provide the necessary environment for developing core components.
- Ultimately the aim is to build up a skilled network across different regions who can provide the necessary support network to ensure the community meets it objectives and is a long term success
- Steps we completed during 2011 to support co-development
- Steps to be completed during 2012:1st qtr:1st set of security rules in place through gated check-in2nd qtr: Peer code reviews on larger developments and incrementally put in place working towards formalising. 2nd qtr: Performance indicators – i.e. how long it takes to complete an action.3rd qtr: Stronger acceptance criteria to ensure more focus is placed on user requirements and move towards a test driven environment4th qtr: All new developments are to have unit tests and provide a list of key existing components that will have coverage by the end of the year4th qtr: Automated UI tests will be introduced for the Browser as it is unlikely to changed considerably since the release of 2.0 in February 2012
- We will hear next from ABS on the current placement of Andy at OECD and the benefits