1. Kuali Research Administration (KRA) Kuali Financial System (KFS) Project Management
Andy Slusar
KRA Project Manager
Cornell University
Jim Thomas
KFS Project Manager
Indiana University

3. Agenda
KRA/KFS Guiding Principles
Productivity Tools
Collaboration & Communication
Project Staffing
KRA/KFS Integration
Open Source Misconceptions

4. Guiding Principles KFS based on Indiana’s FIS KRA based on MIT’s Coeus
Scope Statement is the developments team’s “contract” with functional stakeholders
Functional Changes are approved by the respective Functional Council
Technical Standards are governed by the Kuali Technical Council (KTC)

5. Guiding Principles Maximize commonality of business practices
Make configurable as much as possible given time and resource constraints
Burden of proof falls on advocates for change to show benefits exceed costs
All changes subject to “The Reality Triangle”

6. The Reality Triangle Scope Time Resources (KFS Functional Council)
(Project Mgr)
Resources
(KFS Board)

7. Context
Collaboration

8. Collaboration Tools Project Organization and Coordination
Confluence from Atlassian (wiki pages for documentation, collaboration, etc)
JIRA from Atlassian (task tracking)
Sakai (document sharing, archive, etc)
Omniplan, MS Excel and Project for project plans and Gantt charts
Resource planning sheets

9. A Walk Through Confluence
Collaboration Tools
A Walk Through Confluence

10. Collaboration
Requirements for success
Communications
Governance
Commitment
Respect
Trust

11. Community

12. Communication

13. Problems on your project? Who you gonna call?

14. Kuali Man!!

15. Communications
Communication Plan
Communications Tools
Meetings

16. Choose the appropriate medium
Communication Tools
Choose the appropriate medium
Face to face
Video Conference/Skype
Telephone
Chat

17. Meetings Board Functional Council Technical Council
Project Leadership meetings
Developer meetings
Code Reviews
One on ones
Face to Face meetings
Focus groups
Informal 17

18. Effective Meetings Have an agenda Record Action Items
Track and follow up
Formation of ad hoc subgroups

19. Development Team Sourcing
Project Resources
Role definitions
Development Team Sourcing
Tendered Resources
Onshore consulting
Offshore consulting
Backfill for functional resources
Training

20. KRA/KFS Project Differences
Coeus relationship vs. IU FIS
Team size/project scope
User community differences
Rice Evolution/Extraction
Tool Differences
KRA Functional Team uses Confluence
KFS Functional Team uses Sakai

21. KRA/KFS Integration Team
Define integration points
Static Data
Person Data
Organization Data
Internal
External
Cost Elements
Transactional Data
Proposals
Budgets

22. Open Source Misconceptions
Part time developers
Not industrial strength
Not well tested
Hap-hazard governance
No documentation

23. Kuali Community Source
Full Time Dedicated Development Teams
Dedicated Functional Resources
Built for 24X 7 reliability and built to be scalable for use by the largest institutions
Intensive QA/Testing process
Structured and well documented governance process
Extensive functional and technical documentation
Partner Institutions dedicated to the success of Kuali!
Commercial Affiliates available to provide expertise

24. How are we doing? How will we measure “success”?
Are we delivering working code that provides functionality that meets our SMEs expectations?
Are we meeting our project deadlines?
Do we have successful implementers?

25. Sound like fun?
Want to get more involved? Do you have experienced Java Developers? Do you have functional expertise? or Join the Kuali Partners Program (details at

26. KFS Project Management
Questions?