Agile Development
Agile Software Development - Sound software engineering practices put back into Agile Software Development.
The Agile Software Development initiative aims to pull agile development to the next level. By collecting best practices, develop new solutions where the existing ones do not suffice, and put this together in a suite that allows us to create better software under realistic conditions.
- 4 plus 1 View Model
- A brief history lesion on why we have got HTML5.
- A custom performance testing framework
- About failing agile projects
- Abstract
- Advanced Spring configuration
- Agenda - Final
- Agenda and CASE
- Agile
- Agile 2.0
- Agile 2.0 in the real world (TBA)
- Agile Communities
- Agile Individuals
- Agile Maturity
- Agile Maven quickstart
- Agile Mindset and Methodology
- Agile Organizations
- Agile Project Communication
- Agile Project Management vs Agile Product Management
- Agile Software Development Home
- Agile Tragedy - the agile practitioner visits the wine store
- Agile projects and contracts
- An overview of what we developers struggle with today and how HTML5 can solve parts of those.
- Android
- Android emulator howto
- Articles worth reading
- Attackers
- Attacks
- Audit log
- Automated Deployment Resources
- Automatic code review
- Available native package systems
- Backlog
- Basic configuration tactics
- Basic error handling
- Bridging the gaps-backward compatibility
- Build Android projects with Maven
- Build C (plusplus) code for multiple platforms with Maven
- Build pipeline
- Builder project
- C++ i686 pom
- C++ parent pom
- C++ rpm pom
- C++ x86_64 pom
- CI Feedback gadgets
- CI Setup with Jenkins and GitHub
- CI Strategies
- CI Terminology
- CI for grunt projects
- CI recommendations
- CORS
- CSRF
- Canvas
- Cargo Cult
- Catch oriented exception strategy
- Change environment at build-time using profiles
- Changes from default installation
- Checklist when leaving a project
- Choose a coding standard
- Choose a documentation strategy
- Choose a test strategy
- Choose configuration strategy
- Classic Spring configuration tactics
- Clean code
- Clean code measure overview
- Code and Test Structure when Consuming WebServices
- Code camp challenge
- Code coverage using Surefire, TestNG, Jacoco and Sonar
- Code coverage using Surefire, TestNG, Jacoco and Sonar
- Code organization to support easy removal
- Code review
- Code-centric test tools
- Coding teams
- Collections
- Command line input windows
- Comments from JigZaw frontpage
- Commit Notification
- Common Factor list
- Common reasons for agile project failure
- Company parent pom example for only Java projects
- Comparison of Identity and Authentication products
- Complete code example from demo
- Complete code example in demo
- Conditional requests
- ConfigService
- ConfigService Notes
- ConfigService Notes2
- Configuration Categorization
- Confluence Documentation Template
- Confluence resources
- Confluence-based Documentation Release
- Continuous Deployment
- Continuous Deployment Diagram
- Continuous Integration
- Control at System level
- Control at Systems level
- Control at the application level
- Control state
- Conventions for org
- Copy of Timeline
- CouchDB Simple hosted JSON DB for mobile and js apps
- Crystal Clear
- Daily Standup meeting
- Data-driven testing
- Database versioning
- Debug log
- Definition of Done
- Delivery Team 1
- Delivery Team 2
- Delivery Team 3
- Delivery Team 4
- Deploy AWS Lambda
- Deploy application with Java Network Launching Protocol (JNLP)
- Deploy application with native packages
- Deploy to different environments
- Deploy to different environments - run-time
- Deploy zip to artifact repo with grunt-maven-tasks
- Deployment and Configuration
- Deployment and Configuration Products
- Deployment strategies
- DevOPS and NoOPS comparision
- DevOps
- Developers - Error handling concerns in service or component systems
- Diagram Software
- Distributed Revision Control
- Dive and conquer tactics
- Divide and conquer
- Docker
- Documentation
- Documentation Release
- Documentation team 4
- Documentation team3
- Documentation5
- Domenestruktur og medfølgende egenskaper - et epos
- Download latest Artifact from Nexus
- EMI Server Overview
- Embedded ActiveMQ JMS Server (Spring)
- Endpoint tests
- Enterprise Maven Infrastructure
- Enterprise economy versus Project economy
- Environment
- Environment versioning
- Error Categorization example
- Error Handling And Exception Management
- Error Push Setup
- Evaluation HTML5Code Camp
- Evaluation of HDIV
- Evaluation of tactics according to organizational drivers
- Event-based Logging
- Evo
- Example JSW and RPM
- Example RPM Parent
- Excellent Books
- Exceptions easily provoked
- Executable uber-jar using maven-shade-plugin
- Extreme Agile
- FAQ
- Feature Branches
- Feedback
- Ferris' notes from part 2
- Finally, an Agile test strategy! (that works)
- Find latest version in NEXUS repo
- Flexibility vs complexity trade-off
- Frontend
- GeekCruise Notes - Part 2 - Emil presents Neo4J
- General development tips
- General test theory
- Generic Parent POM Example
- Glossary
- GreenHopper
- Groovy & Grails Topics
- Ground level - Pain
- Groups and when to run them
- Gummy Bears
- HTML 5 Code Camp
- HTML 5 Code Camp Documentation
- HTML 5 Coding Challenge Apps
- HTML5 overview
- HTTP request compression
- HTTP response compression and related security exploits
- Helper Libraries
- How to bridge the gap between Operations and Development
- How to call Oracle stored procedures from Java
- How to combine JigZaw with the V-model
- How to debug webapp performance proactively?
- How to debug webapp performance reactively?
- How to deploy to IBM WebSphere 6.x
- How to do setup and tearDown for a group of tests.
- How to make the output of a shell command available to Maven?
- How to start ActiveMQ JMS Broker in a separate process
- How to start a new operating system process from Java
- How to structure EAR projects?
- How to test remoting in-process
- How to use JUnit Categories to implement JigZaw
- How to use TestNG groups to implement JigZaw
- How to use Unitils for data-driven regression testing
- How to use a zip file to share resources between projects
- IAM - Identity and Access Management
- IAM Terminology
- Identity Management
- Improved communication
- Incorporating best security practices in development
- Index
- Input Validation
- Installation and Deployment Automation
- Introducing JigZaw in your organization
- IoT Security
- Issue tracking in the Enterprise
- Issue workflow
- JMS Testing according to JigZaw
- JMeter configuration
- JMeter pom.xml
- JMeter tutorial
- JPA
- JRuby
- JSW Daemon Parent POM Example
- JSW Daemon Webapp Parent POM Example
- JaMaCU Deployment Strategy
- Java Parent POM Example
- Java SSL - Keystores
- Java Web Application Strategy
- Java Web Frameworks
- JavaScript
- JavaSpaces
- Jetty in a test
- Jetty with pre-populated local HSQLDB
- JigZaw
- JigZaw Categorization Matrix
- JigZaw Design Principles and Drivers
- JigZaw Design Principles and Drivers - OLD
- JigZaw FAQ
- JigZaw Intro
- JigZaw Introduction
- JigZaw Multidimensional Test Categorization
- JigZaw TODO
- JigZaw Test Levels
- JigZaw TimeLine 2
- JigZaw Timeline 3
- JigZaw Verktøy
- JigZaw as architecture improvement enabler
- JigZaw principles applied to test maintenance
- JigZaw results from system test
- JigZaw timeline
- Jira - notes
- Jira Planning, reporting and monitoring
- Jira usage principles
- Just enough upfront design
- KM: Software Development Blog from May, 2021
- Kanban
- Kjartans notes from Emils talk
- Lean
- Levels of identity assurance
- License - the short version
- Lightning talks
- Lightweight Web Application Development
- Lightweight alternatives to heavyweight technologies
- Log Tools
- Logging
- Logging FAQ
- Logical Requirements to Persistence Products
- MS SQL Server
- Main class with embedded jetty
- Make some choices
- Managing test data
- Mapping Jira Concepts to Scrum and version strategy
- Mapping between requirements and tests
- Maven Artifact Naming
- Maven Assemble and Distribute Artifacts FAQ
- Maven Dependencies and Build Stability FAQ
- Maven Deploy and Release FAQ
- Maven FAQ
- Maven FAQ - backup
- Maven FUQ
- Maven Infrastructure
- Maven Other FAQ
- Maven Project Terminology
- Maven Repository Management FAQ
- Maven Test FAQ
- Maven Webstart - JNLP DownloadServlet
- Maven Webstart - static website
- Maven and Spring
- Maven quick-start FAQ
- Maven-based Software Release
- Maximize value of testing
- Measurements and communication
- Messaging in the cloud
- Methods and Methodologies
- Microservices-scalable Front Door
- MongoDB migration
- Monitoring
- Multi-environment Configuration and Deployment Strategy
- Multi-module project with inheritance
- Multi-module project with shared release cycle only
- Navigation
- Nexus configuration tips
- One-click deploy
- Only Service Tests example
- Open Source JMS Server Comparison
- Organize Maven projects and modules FAQ
- Organizing Maven projects
- Other
- Other test tools
- Output Encoding
- Package by feature
- Participant bio and questionaire
- Per-deployment projects
- Performance test
- Performance test tools
- Persistence
- Persistence Product Overview
- Planning Poker
- Platform dependent artifacts
- Pomodoro
- Potentially Excellent books
- Practices
- Pragmatic Programming
- Presentation Logic Controller
- Presentations and Publications
- Presenting Scrum for project managers
- Product specific solutions
- Program detailed - Draft 01
- Programming Ethics
- Project Inheritance
- Project Model and Contracts
- Project Structure for Persistence Logic
- Pull configuration from Central Repo
- Pull deployment script for Windows
- Pull-based Continuous Delivery for Java applications
- Pull-based Continuous Delivery with Java and Docker
- Questions and Answers
- Quotes on Complexity
- RDBMS testing according to JigZaw
- REST
- RESTful authentication
- RPM Deployment with Java Service Wrapper
- RPM-based Installation
- Recommended directory structure using Subversion and Maven
- Recommended reading
- Record-and-playback test automation
- Relational Databases
- Release Profile
- Release process and agility
- Repository Management
- Requirement tests vs code tests
- Resources
- Resources and required reading
- RestoreDefaultState - Oracle database
- Retrospectives
- Risk Management
- Robust smidig utvikling - når resultater er viktigere enn religion
- Roles in agile testing
- Rules for Developing Robust Programs with Java Exceptions
- SQL
- SSOTicket
- Sandbox
- Scaled Agile Framework
- Scratch area
- Script to download and unpack - Windows
- Scrum
- Scrumworks tips
- Security
- Security Resources
- Security recommendations for web application frameworks
- Selenium
- Sequence, flow or dispatcher test
- Setup for Selenium on CI using Maven, Jetty and JUnit
- Shutting down via JMX
- Simple property strategy
- Single-responsibility principle
- Skyggedrift
- Slf4j and logback for error and debug logging
- Smidig20AtSmidig2007
- Smoother Development with Maven FAQ
- Smoother Development with Maven FAQ
- Software Craftsmanship
- Spring TestContext Framework
- Sprint planning
- Stage testing
- Staged Spring
- Standalone angular app with embedded jetty
- Standard security measures
- Start Jetty application with stubbed services
- Start a new JVM from Java
- States of a distributed application
- Stigs Neo4J notes
- Strategies
- Strategy concepts and best practices
- Structuring packages and contexts
- Synchronization between Maven repository and RPM repository
- SysAdmin Production Toolbox
- SysAdmin Test Environment Toolbox
- System Release Standardization
- System Test - Level of automation
- System Test - Logical Overview
- System release archive
- Tactics
- Team 1
- Team 2
- Team 3
- Team 4
- Team 5
- Team 6
- Tech stack for modern frontend
- Technical site and reporting
- Technology for Distributed Contexts
- Terminology
- Test
- Test Frameworks and Tools
- Test groups and phases
- Test nomenclature and classification
- Test pl_sql - old
- Test strategy for Oracle PL_SQL
- Test structure
- Test structure and Single-Responsibility Principle
- Test-Driven Development
- TestNG
- TestNG run only database tests example
- TestNG vs JUnit
- Testing DB scripts
- Testing Data Bound components
- Text compare in Windows
- The Diary
- The Planning Game
- The intrusiveness blacklist
- The new form elements, attributes and input validation.
- The new semantic elements (section, article, nav etc..).
- Thoughts on architecture when using HTTP endpoints
- Time Tokens
- Timeline
- Tomcat production setup
- Tools
- Tools and implementation
- Tools for data(base)-driven testing
- Typical application architecture
- Unitils Test class example
- Unitils pom.xml example
- Upstream-downstream relationship applied to User Stories
- User Stories
- User Story Mapping
- User documentation for a software product
- User ticket solutions
- Using Jira for agile development
- V-model vs JigZaw
- Verify expected behavior instead of looking for bugs
- Version Control Strategies for Confluence-based Documentation
- Versioning
- Video and Audio
- Visualize Maven modules
- W3C Widgets
- Waterfall - why and why not?
- Web Application Architecture
- Web Application Exception Management
- Web Application Fragments
- Web Application JigZaw
- Web Application Logging
- Web Application Security
- Web Design
- Web SQL - IndexedDB
- Web application container pull deployment
- Web development tips and tricks
- Web framework security tactics
- Web test tools
- Web testing
- WebSockets
- WebSphere deployment from a CI environment
- Webapp caching strategy
- Webapp deployment from RPM
- Webapp deployment from RPM - scratch area
- What is Agile 2.0? Isn't 1.0 enough?
- When to use JigZaw
- Word Documentation Template
- XP
- Zero downtime deployment with ECS
- assembly.xml to create zip with support for config_override
- logback.xml example
- pom.xml yeoman and embedded jetty
- rpm-maven-plugin with multiple modules