import { Duration, RemovalPolicy, Stack, StackProps } from 'aws-cdk-lib'; | |
import { Repository, IRepository } from 'aws-cdk-lib/aws-codecommit'; | |
import { Construct } from 'constructs'; | |
import { BlockPublicAccess, Bucket } from 'aws-cdk-lib/aws-s3'; | |
import { ARecord, HostedZone, IHostedZone, RecordTarget, ZoneDelegationRecord } from 'aws-cdk-lib/aws-route53'; | |
import { AllowedMethods, Distribution, OriginAccessIdentity, SecurityPolicyProtocol, ViewerProtocolPolicy } from 'aws-cdk-lib/aws-cloudfront'; | |
import { Artifact,Pipeline } from 'aws-cdk-lib/aws-codepipeline'; | |
import { CloudFormationCreateUpdateStackAction, CodeBuildAction, CodeCommitSourceAction, S3DeployAction } from 'aws-cdk-lib/aws-codepipeline-actions'; | |
import { PipelineProject, BuildSpec, LinuxBuildImage } from 'aws-cdk-lib/aws-codebuild'; | |
import { CodePipeline as CodePipelineTarget } from 'aws-cdk-lib/aws-events-targets'; |
Just a user story with some acceptance criteria is not enough when estimating stories that you implement in AWS cloud
Scrum way of doing things delays lots of design decisions into planning I - When you work with software defined infrastructure, you need to do a design earlier in the process on, in order to get results that match with reality.
When Scrum and user stories were invented, infrastructure was a given thing and features assumed it to be. At some point in time, a server was purchased or rented and this was a given set of ressources then.
- Scrum and Extreme Programming from the Trenches Download
- Essential Skill of Agile Development Download
- Agile Patterns - The technical Cluster Download
- Scrum Checklists Download
- Extreme Programming Download
- Agile Software Development Methods - Review and Analysis Download
- An introduction to Agile software Management Download
- The Art of Agile Development Download
- An introduction to Agile Methods Download
- Agile Software Development [Download](https://www.thedacs.com
- a meta book
- not using buzzwords (like agile)
- has concrete references
- avoids rulkes, laws atc that are stemming from (western) philosopy
- explains why these rules are no rules
- Gives examples for practices in inccremental and iterative organizations
- no sudo religious BS
- adhere to maslow (eating/sex > recreational learning)
Es gibt weit weniger neu ausgebildete Informatiker und Software Entwickler als der 'Markt' benötigt. Die schafft einen 'Sellers Market', wo die Anbieter die Bedingungen diktieren.
Leider scheinen dies wenige Unternehmen anzuerkennen, so scheinen mir doch diverse Haltungen und Forderungen im Umgang mit Neulingen eher vom 'alten Geist' geprägt. Anzeichen hierfür