Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Best practices for team dev in single org by Mind Map: Best practices for team dev in
single org
0.0 stars - reviews range from 0 to 5

Best practices for team dev in single org

Mop-up: App lifecycle

Trying is OK, but we need to keep it neat & lean

Clean up happens as often as releases

20% of time allocated to it

Weed-out the old stuff

Use reports & dashboards to check utilization:

whatever isn't used - Delete it, grace period, hide & delete

Integration / Jenkins

Dev has 3 codelines

Main

Patch

Freeze

Continuous jenkins integration

Release process

every 2 weeks

Frequent + Swiss watch precision

Scope could vary but schedule doesn't

no matter what, *you will release in 2 weeks", your code will be in production

process

1. DE org

2. Staging

3. Release staging

4. Integration, merge code from other teams

5. Production

fast pace ensures no big chunks of development

dev & release process in action:

image

Proper code review practices

mandatory

name of reviewer is required at check-in

no development of new features before all bugs are fixed

Coding guidelines

You are a community, consistency is key

How? Empower guest teams

let the teams manage their own dev env

A solid product owner

from the requestor's group

single point of contact on

stakeholders

customers/users

establish long term vision

user stories

dev core team

manages the Change Review meetings

every 2 weeks

questions:, What is the feature, What is the benefit, Who is the customer, Does it align wit the corporate vision, Do users/stakeholders agree with priority?, How are you planning to implement this?, Why not consider another design?

Must have success metrics