SlideShare uma empresa Scribd logo
1 de 29
Baixar para ler offline
Linaro
Connect,
Hong Kong
March 2013
Linaro Requirements Lifecycle
Kate Stewart and Kanta Vekaria
www.linaro.org
Idea to Deliverable
ENGIN
EERIN
G
DELIVE
RABLE
www.linaro.org
Backlog Processing
MEMBER
CONFIDENTIAL?
STEERING
COMMITTEE
BACKLOG
LANDING
TEAM
BACKLOG
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
www.linaro.org
Team Investigation Before SC Review
MEMBER
SPONSORED?
Linaro+SC
CARD
DRAFTING
PRIVATE
CARD
DRAFTING
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?
www.linaro.org
Member Sponsored Card
Member &
Linaro Team
Agree on
Proposal ?
PRIVATE
CARD
DRAFTING
Linaro+SC
CARD
DRAFTING
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
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.
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
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
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
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
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
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
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
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.
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.
Linaro
Connect,
Hong Kong
March 2013
Questions?
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
www.linaro.org
Epics vs. Cards?
EPIC
CARD
CARD
CARD
Steering
Committee
(SC)
Operational
Sub Committee
(OPSCOM)
implemented by
implemented by
implemented by
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.
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
www.linaro.org
TSC & OPSCOM:
Roadmap management
Process Management
Restrospective
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.
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
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
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
www.linaro.org
Open Questions: Retrospective.
Questions:
- any concerns with R&R listed?
- what worked?
- what needs to be improved?

Mais conteúdo relacionado

Mais de Linaro

HPC network stack on ARM - Linaro HPC Workshop 2018
HPC network stack on ARM - Linaro HPC Workshop 2018HPC network stack on ARM - Linaro HPC Workshop 2018
HPC network stack on ARM - Linaro HPC Workshop 2018
Linaro
 
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
Linaro
 
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
Linaro
 
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainlineHKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
Linaro
 
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainlineHKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
Linaro
 
HKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
HKG18- 115 - Partitioning ARM Systems with the Jailhouse HypervisorHKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
HKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
Linaro
 
HKG18-TR08 - Upstreaming SVE in QEMU
HKG18-TR08 - Upstreaming SVE in QEMUHKG18-TR08 - Upstreaming SVE in QEMU
HKG18-TR08 - Upstreaming SVE in QEMU
Linaro
 
HKG18-120 - Devicetree Schema Documentation and Validation
HKG18-120 - Devicetree Schema Documentation and Validation HKG18-120 - Devicetree Schema Documentation and Validation
HKG18-120 - Devicetree Schema Documentation and Validation
Linaro
 
HKG18-223 - Trusted FirmwareM: Trusted boot
HKG18-223 - Trusted FirmwareM: Trusted bootHKG18-223 - Trusted FirmwareM: Trusted boot
HKG18-223 - Trusted FirmwareM: Trusted boot
Linaro
 
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
Linaro
 
HKG18-317 - Arm Server Ready Program
HKG18-317 - Arm Server Ready ProgramHKG18-317 - Arm Server Ready Program
HKG18-317 - Arm Server Ready Program
Linaro
 

Mais de Linaro (20)

Huawei’s requirements for the ARM based HPC solution readiness - Joshua Mora
Huawei’s requirements for the ARM based HPC solution readiness - Joshua MoraHuawei’s requirements for the ARM based HPC solution readiness - Joshua Mora
Huawei’s requirements for the ARM based HPC solution readiness - Joshua Mora
 
Bud17 113: distribution ci using qemu and open qa
Bud17 113: distribution ci using qemu and open qaBud17 113: distribution ci using qemu and open qa
Bud17 113: distribution ci using qemu and open qa
 
OpenHPC Automation with Ansible - Renato Golin - Linaro Arm HPC Workshop 2018
OpenHPC Automation with Ansible - Renato Golin - Linaro Arm HPC Workshop 2018OpenHPC Automation with Ansible - Renato Golin - Linaro Arm HPC Workshop 2018
OpenHPC Automation with Ansible - Renato Golin - Linaro Arm HPC Workshop 2018
 
HPC network stack on ARM - Linaro HPC Workshop 2018
HPC network stack on ARM - Linaro HPC Workshop 2018HPC network stack on ARM - Linaro HPC Workshop 2018
HPC network stack on ARM - Linaro HPC Workshop 2018
 
It just keeps getting better - SUSE enablement for Arm - Linaro HPC Workshop ...
It just keeps getting better - SUSE enablement for Arm - Linaro HPC Workshop ...It just keeps getting better - SUSE enablement for Arm - Linaro HPC Workshop ...
It just keeps getting better - SUSE enablement for Arm - Linaro HPC Workshop ...
 
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
Intelligent Interconnect Architecture to Enable Next Generation HPC - Linaro ...
 
Yutaka Ishikawa - Post-K and Arm HPC Ecosystem - Linaro Arm HPC Workshop Sant...
Yutaka Ishikawa - Post-K and Arm HPC Ecosystem - Linaro Arm HPC Workshop Sant...Yutaka Ishikawa - Post-K and Arm HPC Ecosystem - Linaro Arm HPC Workshop Sant...
Yutaka Ishikawa - Post-K and Arm HPC Ecosystem - Linaro Arm HPC Workshop Sant...
 
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
Andrew J Younge - Vanguard Astra - Petascale Arm Platform for U.S. DOE/ASC Su...
 
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainlineHKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
 
HKG18-100K1 - George Grey: Opening Keynote
HKG18-100K1 - George Grey: Opening KeynoteHKG18-100K1 - George Grey: Opening Keynote
HKG18-100K1 - George Grey: Opening Keynote
 
HKG18-318 - OpenAMP Workshop
HKG18-318 - OpenAMP WorkshopHKG18-318 - OpenAMP Workshop
HKG18-318 - OpenAMP Workshop
 
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainlineHKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
HKG18-501 - EAS on Common Kernel 4.14 and getting (much) closer to mainline
 
HKG18-315 - Why the ecosystem is a wonderful thing, warts and all
HKG18-315 - Why the ecosystem is a wonderful thing, warts and allHKG18-315 - Why the ecosystem is a wonderful thing, warts and all
HKG18-315 - Why the ecosystem is a wonderful thing, warts and all
 
HKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
HKG18- 115 - Partitioning ARM Systems with the Jailhouse HypervisorHKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
HKG18- 115 - Partitioning ARM Systems with the Jailhouse Hypervisor
 
HKG18-TR08 - Upstreaming SVE in QEMU
HKG18-TR08 - Upstreaming SVE in QEMUHKG18-TR08 - Upstreaming SVE in QEMU
HKG18-TR08 - Upstreaming SVE in QEMU
 
HKG18-113- Secure Data Path work with i.MX8M
HKG18-113- Secure Data Path work with i.MX8MHKG18-113- Secure Data Path work with i.MX8M
HKG18-113- Secure Data Path work with i.MX8M
 
HKG18-120 - Devicetree Schema Documentation and Validation
HKG18-120 - Devicetree Schema Documentation and Validation HKG18-120 - Devicetree Schema Documentation and Validation
HKG18-120 - Devicetree Schema Documentation and Validation
 
HKG18-223 - Trusted FirmwareM: Trusted boot
HKG18-223 - Trusted FirmwareM: Trusted bootHKG18-223 - Trusted FirmwareM: Trusted boot
HKG18-223 - Trusted FirmwareM: Trusted boot
 
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
HKG18-500K1 - Keynote: Dileep Bhandarkar - Emerging Computing Trends in the D...
 
HKG18-317 - Arm Server Ready Program
HKG18-317 - Arm Server Ready ProgramHKG18-317 - Arm Server Ready Program
HKG18-317 - Arm Server Ready Program
 

Último

Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
WSO2
 
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Victor Rentea
 

Último (20)

Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost SavingRepurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
 
Exploring Multimodal Embeddings with Milvus
Exploring Multimodal Embeddings with MilvusExploring Multimodal Embeddings with Milvus
Exploring Multimodal Embeddings with Milvus
 
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ..."I see eyes in my soup": How Delivery Hero implemented the safety system for ...
"I see eyes in my soup": How Delivery Hero implemented the safety system for ...
 
Six Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal OntologySix Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal Ontology
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
MINDCTI Revenue Release Quarter One 2024
MINDCTI Revenue Release Quarter One 2024MINDCTI Revenue Release Quarter One 2024
MINDCTI Revenue Release Quarter One 2024
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...
 
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
 
Introduction to use of FHIR Documents in ABDM
Introduction to use of FHIR Documents in ABDMIntroduction to use of FHIR Documents in ABDM
Introduction to use of FHIR Documents in ABDM
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
Vector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptxVector Search -An Introduction in Oracle Database 23ai.pptx
Vector Search -An Introduction in Oracle Database 23ai.pptx
 
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024Finding Java's Hidden Performance Traps @ DevoxxUK 2024
Finding Java's Hidden Performance Traps @ DevoxxUK 2024
 
Spring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUKSpring Boot vs Quarkus the ultimate battle - DevoxxUK
Spring Boot vs Quarkus the ultimate battle - DevoxxUK
 
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
 
JohnPollard-hybrid-app-RailsConf2024.pptx
JohnPollard-hybrid-app-RailsConf2024.pptxJohnPollard-hybrid-app-RailsConf2024.pptx
JohnPollard-hybrid-app-RailsConf2024.pptx
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)
 

LCE13: Linaro Requirements Lifecycle

  • 1. Linaro Connect, Hong Kong March 2013 Linaro Requirements Lifecycle Kate Stewart and Kanta Vekaria
  • 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.
  • 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?