23. 23
Cloud Foundry CLI Product
• Exposes CF features
• To Devs and Admins
• One CLI for all CF offerings
• 6-13,000 downloads
per day
• Releasing monthly
• 5 platforms
Copyright 2016 FUJITSU LIMITED
25. 25
Fujitsu Flavour to CLI
• Raised focus on “Enterprise” use and “Professional” look
– Installation & use in corporate environments
– Security & Integrity
– Prompt reaction to regressions
– Long term compatibility
– Professional looking help, docs
– Multi-language
– Consistency
Copyright 2016 FUJITSU LIMITED
26. 26
Cloud Foundry CLI Workflow 1/2
1. PM gathers requirements:
– Requests from other PMs/teams
– From users on GitHub, CF Dev, Slack; Stakeholders
– Product comparisons
2. PM writes stories, Google doc
3. Discussions (team, external expertise, requesters)
4. Prioritize, release planning
5. Discuss at weekly pre-IPM with anchor
Copyright 2016 FUJITSU LIMITED
27. 27
Cloud Foundry CLI Workflow 2/2
6. Discuss at IPM with whole team
– Pointing of 2 weeks’ worth of stories
– Reprioritize if too complex/time consuming
7. Devs implement
– Clarify UX questions (slack, comment on story)
– Delivers one by one, automated edge builds
8. PM acceptance (accept if OK, reject if anything unexpected)
9. Just before release:
– PM prepares release notes
– Devs create the release
Copyright 2016 FUJITSU LIMITED
28. 28
Cloud Foundry CLI Challenges
• Consistent, smooth UX
• Access to end-users (users vs. enterprise customers)
• Keeping up (5 in CLI team, 10x that in CF components)
• Compatibility (fortnightly CF releases)
• Regressions (153 commands!)
• Technical Debt
• Priorities, feature-creep, core vs plug-ins
• Various platforms & environments (e.g. proxies, DNS)
• Localization
Copyright 2016 FUJITSU LIMITED
29. 29
Cloud Foundry CLI Upsides
• Brilliant team
• Agile mindset embraces
sudden changes
• Devs’ full focus on
development
• Pairing, no separate reviews
and documents
• Advanced tools
(github, tracker, slack, appear.in)
• Sympathetic users,
stakeholders
• Foundation support
• End-users
Copyright 2016 FUJITSU LIMITED