1.
Linaro
Connect,
Hong Kong
March 2013
Linaro Requirements Lifecycle
Kate Stewart and Kanta Vekaria

2.
www.linaro.org
Idea to Deliverable
ENGIN
EERIN
G
DELIVE
RABLE

3.
www.linaro.org
Backlog Processing
MEMBER
CONFIDENTIAL?
STEERING
COMMITTEE
BACKLOG
LANDING
TEAM
BACKLOG

4.
www.linaro.org
Steering Committee Responsibilities
WHICH
TEAM?
● LEG-SC: Enterprise
● LNG-SC: Networking
● TSC: Android
● TSC: Kernel
● TSC: Power Management
● TSC: Graphics
● TSC: Toolchain
● TSC: Virtualization
● TSC: Builds and Baselines
● TSC: LAVA
● TSC: QA
● TSC: OCTO topics

5.
www.linaro.org
Team Investigation Before SC Review
MEMBER
SPONSORED?
Linaro+SC
CARD
DRAFTING
PRIVATE
CARD
DRAFTING

6.
www.linaro.org
Information for a well formed request
● Overview: 1 liner of what is being requested.
● Details: Description, with links to relevant information, and
contacts to help clarify roadmap request.
● Confidentiality Level: Private, Linaro+SC, none
○ is there member confidential data in this request?
○ can it be shared with other members or public?
● Source: Who made original request?
● Member(s) Interest Level: Sponsor(s)?
● Date request made?
● Date needed by? (if known)
● Subsystem(s) and teams impacted?
● Steering committee jurisdiction?

7.
www.linaro.org
Member Sponsored Card
Member &
Linaro Team
Agree on
Proposal ?
PRIVATE
CARD
DRAFTING
Linaro+SC
CARD
DRAFTING

8.
www.linaro.org
New Roadmap Card Scope Assessment
Linaro+SC
CARD
DRAFTING
>3 months
or
multiple teams
or
new area
?
Linaro+SC
EPIC
DRAFTING
Linaro+SC
CARD
DRAFTING
SC
OPSCOM

9.
www.linaro.org
Steering Committee (SC)
Role:
○ Member nominees provide guidance on priorities for technical
resources.
Responsibilities:
○ Formal sponsorship of roadmap requests
○ Review and prioritize strategic new efforts and changes at EPIC
level (>3 person months of effort)
○ Periodic review of ongoing activities
○ Roadmap publishing scope determination
○ Topic roadmap approval
Meets:
○ Every 2 weeks.

10.
www.linaro.org
Operational Sub Committee (OPSCOM)
Role:
○ Member nominees provide tactical feedback implications of
roadmap changes
Responsibilities:
○ Review new roadmap CARDs in approved EPICs
○ Review closeout material on CARDs for issues.
○ Review changes to CARDs (state & date), and provide feedback if
there are implications to projects that members have a
dependency on.
Meets:
○ Start of month, on week TSC does not meet.
Documented:
https://wiki.linaro.org/OPSCOM/RoadmapProcessWithJIRA

11.
www.linaro.org
CARD State Change
CARD
DRAFTING
CARD
DRAFTING
CARD
PLANNING
CARD
ENGINEERING
CARD
DELIVERED
SC or
OPSCOM
CLOSING-OUT
SC or
OPSCOM
REVIEW
OPSCOM
REVIEW
OPSCOM
REVIEW

12.
www.linaro.org
Roadmap CARD vs. JIRA states: mapping
Roadmap CARD JIRA equivalent Meaning
Concept Drafting Strategic direction and topic identified to have further planning, before
resourcing and prioritization decision can be made. Preliminary
JIRA/blueprints and artifacts may exist but they are being drafted.
Forecast date is for rough target want to aim for.
Approved Drafting The TSC has reviewed the concept and has prioritized the EPIC with
timescale and resource limits. Roadmap cards that need to be
associated with the Approved Concept EPIC can proceed at the
engineering/OPSCOM review level.
Planning Planning Planning has been done for a task, JIRA card/Blueprints exist and
resource estimates and gating dependencies are known. Owner team
has been identified and TSC agreed prioritization has been secured.
Some preliminary development maybe in progress. Forecast date
may change based on when dependencies are met.
Development Engineering Engineering teams are actively working on the task. Expectation is that
resources are available and dependencies have been met and forecast
date reflects high confidence.
Released Delivered Work item has been made available to target audience (Members or
Public) and all associated artifacts are updated to reflect status. (JIRA
cards, Blueprints, etc. have the correct status).
see: https://wiki.linaro.org/Process/Roadmap/Key

13.
www.linaro.org
Consolidation
Storage
Linux kernel
Android upstreaming
Example: Kernel Roadmap
Q1 Q2 Q3 Q4 FutureQ1 Q2
2013 2014
30-June-2013
OOM killer to Staging
Key Reset to Mainline
RAM console to AOSP
ashmem compat_ioctl to Staging
sync driver to Staging
alarm-dev compat_ioctl to Staging logger
single kernel binary
eMMC power mgmt
System Trace Macrocell
TrustZone
Unified probing & mgmt
EPIC: eMMC feature enablement
EPIC: improve&validate f2fs
ASHMEM to Mainline
ARMv8 kexec and kernel crashdump
uprobes support
Fastboot ARMv8-A uprobes and kprobes
Q3 Q4
Released
Development
Planning
Concept
Approved

14.
www.linaro.org
Roadmap Keys
29-June-2013
Members Only
Released
Development
Planning
Concept
Approved
Community
Ongoing
Upstream
Released
Development
Concept
Ongoing
Community/
External
Approved
Planning
Upstream
For more information, see definitions in: https://wiki.linaro.
org/Process/Roadmap/Key
- or -
just click on the links beside the symbols in the key

15.
www.linaro.org
Landing Team Backlog
Member Contact
ARM kanta.vekaria@linaro.org
ST kanta.vekaria@linaro.org
Huawei/HiSilicon usman.ahmad@linaro.org
Fujitsu usman.ahmad@linaro.org
Samsung anmar.oueja@linaro.org
Broadcom glen.valante@linaro.org
Plan to capture and manage
Landing Team requirements
as CARDs in near future
ENGIN
EERIN
G
DELIVE
RABLE

16.
www.linaro.org
Linaro Roadmaps: publishing states
● Public:
○ site: https://wiki.linaro.org/TSC/Roadmaps
○ Engineering: Toolchain, Kernel, Graphics, Virtualization
○ Platforms: LAVA, QA, Builds & Baselines
○ Linaro Enterprise Group (LEG)
● In Development:
○ site: https://wiki.linaro.org/Internal/TSC/DraftRoadmaps
○ Android - voting to keep members-only visible
○ Power Management - in discussion with TSC
○ Linaro Networking Group - in development

17.
www.linaro.org
Linaro Processes: further reading
● https://wiki.linaro.org/Internal/TSC/FeatureRequests
○ Pending Feature Requests (to be updated after connect)
● https://wiki.linaro.org/OPSCOM/RoadmapProcessWithJIRA
○ Has more detailed state diagrams
○ Has information model
○ Has standard templates
● https://wiki.linaro.org/Process/Roadmap
NOTE: documentation updates are in progress, and we'll aim to
keep these sites up to date with any further process tuning.

18.
www.linaro.org
Next Steps?
● Finish transition from Launchpad blueprints to JIRA.
● Landing teams using same CARD infrastructure.
● Get automated reporting of status.
● Introduce member specific summary reporting on CARDs
of interest.

19.
Linaro
Connect,
Hong Kong
March 2013
Questions?

20.
More about Linaro: http://www.linaro.org/about/
More about Linaro engineering: http://www.linaro.org/engineering/
How to join: http://www.linaro.org/about/how-to-join
Linaro members: www.linaro.org/members

21.
www.linaro.org
Epics vs. Cards?
EPIC
CARD
CARD
CARD
Steering
Committee
(SC)
Operational
Sub Committee
(OPSCOM)
implemented by
implemented by
implemented by

22.
www.linaro.org
Linaro Roadmaps: orientation
● public roadmaps: https://wiki.linaro.org/TSC/Roadmaps
○ approved by TSC to be shared
○ reflect what is in JIRA on date published
○ updated when significant changes (at least every interval)
● draft roadmaps: https://wiki.linaro.org/Internal/TSC/DraftRoadmaps
○ only for sharing with TSC members and Linaro employees
○ in discussion, may change
● governance:https://wiki.linaro.org/OPSCOM/RoadmapProcessWithJIRA
○ TSC - strategic changes at EPIC level, roadmap
publishing approval, sponsorship of cards
○ OPSCOM - tactical, monthly updates in JIRA of roadmap
cards from teams reviewed.

23.
www.linaro.org
LINARO Requirements Lifecycle
OUTLINE:
- request-> team backlog -> roadmap ->engineering ->
release.
- where do decisions get made sc/opscom
- open vs. member landing team.
- what makes up a good requirement for sc/opscom
- card state change
- understanding the symbols on the roadmap.
- Questions/FAQ
- trustzone roadmap is going to be of interest

24.
www.linaro.org
TSC & OPSCOM:
Roadmap management
Process Management
Restrospective

25.
www.linaro.org
Steering Committee (SC)
Role:
○ Member nominees provide guidance on priorities for technical
resources.
Responsibilities:
○ Formal sponsorship of roadmap requests
○ Review and prioritize strategic new efforts and changes at EPIC
level (>3 person months of effort)
○ Periodic review of ongoing activities
○ Roadmap publishing scope determination
○ Topic roadmap approval
Meets:
○ Every 2 weeks.

26.
www.linaro.org
Operational Sub Committee (OPSCOM)
Role:
○ Member nominees provide tactical feedback implications of
roadmap changes
Responsibilities:
○ Review new roadmap CARDs in approved EPICs
○ Review closeout material on CARDs for issues.
○ Review changes to CARDs (state & date), and provide feedback if
there are implications to projects that members have a
dependency on.
Meets:
○ Start of month, on week TSC does not meet.
Documented:
https://wiki.linaro.org/OPSCOM/RoadmapProcessWithJIRA

27.
www.linaro.org
New Roadmap Card Scope Assessment
Linaro+SC
CARD
DRAFTING
>3 months
or
multiple teams
or
new area
?
Linaro+SC
EPIC
DRAFTING
Linaro+SC
CARD
DRAFTING
SC
OPSCOM

28.
www.linaro.org
CARD State Change
CARD
DRAFTING
CARD
DRAFTING
CARD
PLANNING
CARD
ENGINEERING
CARD
DELIVERED
SC or
OPSCOM
CLOSING-OUT
SC or
OPSCOM
REVIEW
OPSCOM
REVIEW
OPSCOM
REVIEW

29.
www.linaro.org
Open Questions: Retrospective.
Questions:
- any concerns with R&R listed?
- what worked?
- what needs to be improved?